_ registry / mcp http-sse · checked 1h ago

jp-entity-evidence

https://jp-entity-evidence-production.mk-career-planning.workers.dev

Registry code: 8050ffe570bb498d

api record

Japanese public records on an organization: FSA, MOF, EDINET, ISA and gBizINFO lists. Evidence only.

from a public catalogue that lists it, not from the operator

endpoint
https://jp-entity-evidence-production.mk-career-planning.workers.dev/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is jp-entity-evidence live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is jp-entity-evidence free to use?
Yes — the hub reached it with no key and no payment.
What tools does jp-entity-evidence have?
3 tools: entity_evidence_check, get_receipt, catalog.
Is jp-entity-evidence safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
754ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 open 2 never probed 1 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • catalog open 1h ago

    List the tools of this server with prices, data sources, licensing, daily limits and data freshness.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • entity_evidence_check unknown 1h ago

    For checks spanning several Japanese registries at once: FSA registers, warnings and enforcement case list, MOF asset-freeze list, EDINET filings, ISA support organizations, gBizINFO where connected. Returns each registry's status, version date, source, matches and what was not checked; a domain alone stays unverified. For one registry, use jp-finance, jp-sanctions, jp-edinet or jp-ssw-support-orgs. Stated scope and dates only; no match is not proof none exists. No compliance determination.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 200,
          "description": "Organization name, e.g. 株式会社SBI証券. A person-like name is screened only against the MOF list"
        },
        "detail": {
          "anyOf": [
            {
              "type": "boolean"
            },
            {
              "enum": [
                "0",
                "1",
                "true",
                "false"
              ],
              "type": "string"
            }
          ],
          "description": "true: all records and receipts (default compact)"
        },
        "domain": {
          "type": "string",
          "maxLength": 300,
          "description": "Optional website domain, e.g. example.com. Never resolved to an organization (identity.domain is unverified)"
        },
        "prefecture": {
          "type": "string",
          "maxLength": 20,
          "description": "Prefecture to narrow the ISA and gBizINFO name searches, e.g. Tokyo"
        },
        "edinet_code": {
          "type": "string",
          "maxLength": 10,
          "description": "EDINET filer code, e.g. E03816"
        },
        "address_hint": {
          "type": "string",
          "maxLength": 100,
          "description": "Part of the address, e.g. 千代田区, to tie a name to one gBizINFO corporate number"
        },
        "corporate_number": {
          "type": "string",
          "maxLength": 20,
          "description": "13-digit corporate number, e.g. 3010401049814 (NTA registry not yet connected)"
        },
        "registration_numbers": {
          "type": "object",
          "properties": {
            "fsa": {
              "type": "string",
              "maxLength": 80,
              "description": "FSA registration number, e.g. 関東財務局長(金商)第44号"
            },
            "ssw": {
              "type": "string",
              "maxLength": 30,
              "description": "ISA registered support organization number, e.g. 19登-000002"
            }
          },
          "description": "Registration numbers by registry"
        },
        "fsa_registration_number": {
          "type": "string",
          "maxLength": 80,
          "description": "GET form of registration_numbers.fsa"
        },
        "ssw_registration_number": {
          "type": "string",
          "maxLength": 30,
          "description": "GET form of registration_numbers.ssw"
        }
      }
    }
    arguments 79 lines
  • get_receipt unknown 1h ago

    Re-fetch the stored result of a settled paid call by its receipt_id, for when the response was lost after payment. Free. Unknown or unsettled receipt ids return RECEIPT_NOT_FOUND. Results are kept for 90 days after settlement.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "receipt_id"
      ],
      "properties": {
        "receipt_id": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "The receipt_id returned with a paid result (\"rcpt_\" + 64 hex characters)."
        }
      }
    }
    arguments 15 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 8050ffe570bb498d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8050ffe570bb498d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/8050ffe570bb498d/badge.svg)](https://brick.blue/agent/8050ffe570bb498d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.