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

jp-corporate

https://jp-corporate.plugrail.dev

Registry code: ec8a9a5952b409df

api record

Japanese corporate number lookup using official National Tax Agency public data.

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

endpoint
https://jp-corporate.plugrail.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-corporate live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is jp-corporate free to use?
Yes — the hub reached it with no key and no payment.
What tools does jp-corporate have?
6 tools: search_corporate_by_name, search_corporate_by_number, company_profile, lookup_corporate, search_corporate_by_address, verify_invoice_number.
Is jp-corporate 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
98.7%

90 days 98.8%· all time 98.8%

latency
833ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 322 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
finance & markets company & filings
used for
  • look up japanese corporate number
  • search japanese companies by name
  • verify qualified invoice number
  • get company profile
takes → gives
text → data
tools
6 reads
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 of 6 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.

  • search_corporate_by_name reads unknown 19h ago

    都道府県＋法人名の接頭辞で日本の法人を検索します。国税庁公開データに基づきます。入力例: {"prefecture": "13", "prefix": "渋谷", "limit": 10}

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "prefecture",
    "prefix"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "取得件数 1〜20（省略時は10）。例: 10"
    },
    "cursor": {
      "type": "string",
      "description": "前回応答の nextCursor（透過・省略可）。"
    },
    "prefix": {
      "type": "string",
      "minLength": 1,
      "description": "検索接頭辞（非空）。例: \"渋谷\""
    },
    "prefecture": {
      "type": "string",
      "pattern": "^\\d{2}$",
      "description": "都道府県コード2桁。例: \"13\"（東京）"
    }
  }
}
    arguments 30 lines
  • search_corporate_by_number reads unknown 19h ago

    法人番号（13桁）で日本の法人を1件検索します。国税庁公開データに基づきます。入力例: {"corporateNumber": "1180301018771"}

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "corporateNumber"
  ],
  "properties": {
    "corporateNumber": {
      "type": "string",
      "pattern": "^\\d{13}$",
      "description": "13桁の法人番号。例: \"1180301018771\""
    }
  }
}
    arguments 14 lines
  • company_profile reads unknown 15h ago

    法人番号（13桁）で基本情報・補助金・届出・財務の会社プロファイルを返す。各領域の出典・鮮度・欠損を保持し、部分障害時は取得済みと欠損を同時に返す。入力例: {"corporateNumber": "1180301018771"}

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "corporateNumber"
  ],
  "properties": {
    "corporateNumber": {
      "type": "string",
      "description": "13桁の法人番号。例: \"1180301018771\""
    }
  }
}
    arguments 13 lines
  • lookup_corporate reads unknown 19h ago

    法人番号の確定照会と名称・所在地の候補探索を分離して返す。名称だけでは断定せず複数候補と根拠別scoreを返す。候補探索は name 指定時は prefecture 任意（省略時は全国前方一致で searchedNationwide:true・候補に県コード付き・県か住所を足すと絞り込める）。prefecture は '13' または '東京都' のどちらでも可。address が「東京都渋谷区…」のように都道府県名で始まれば prefecture は省略可（推定）。address のみの検索は prefecture または推定が必須（全国非対応）。番号確定例: {"corporateNumber": "1180301018771"}／候補例: {"name": "渋谷", "prefecture": "13", "limit": 10}／全国例: {"name": "山田工業"}

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1,
      "description": "法人名の検索語（候補探索）。例: \"渋谷\""
    },
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "取得件数 1〜20（省略時は10）"
    },
    "cursor": {
      "type": "string",
      "description": "前回応答の nextCursor（透過・省略可）。"
    },
    "address": {
      "type": "string",
      "minLength": 1,
      "description": "所在地の絞込語（候補探索の任意）。例: \"渋谷\""
    },
    "prefecture": {
      "anyOf": [
        {
          "type": "string",
          "minLength": 1
        },
        {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": -9007199254740991
        }
      ],
      "description": "都道府県（name 指定時は任意・省略時は全国検索。address のみのときは必須。address 先頭の都道府県名から推定できれば省略可）。JISコード \"13\"・13・\"1\" または都道府県名 \"東京都\"・\"東京\" のどちらでも可"
    },
    "corporateNumber": {
      "type": "string",
      "pattern": "^\\d{13}$",
      "description": "13桁の法人番号（確定照会）。例: \"1180301018771\""
    }
  }
}
    arguments 45 lines
  • search_corporate_by_address reads unknown never probed

    都道府県＋所在地の接頭辞で日本の法人を検索します。国税庁公開データに基づきます。市区町村名の前方一致が主経路で、町名以降を含む指定（例: 港区港南・東京都港区港南）は住所全文の前方一致へ迂回し、町名のみの断片（例: 港南）は住所全文の部分一致で拾います。入力例: {"prefecture": "13", "prefix": "渋谷", "limit": 10}

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "prefecture",
    "prefix"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "取得件数 1〜20（省略時は10）。例: 10"
    },
    "cursor": {
      "type": "string",
      "description": "前回応答の nextCursor（透過・省略可）。"
    },
    "prefix": {
      "type": "string",
      "minLength": 1,
      "description": "検索接頭辞（非空）。例: \"渋谷\""
    },
    "prefecture": {
      "type": "string",
      "pattern": "^\\d{2}$",
      "description": "都道府県コード2桁。例: \"13\"（東京）"
    }
  }
}
    arguments 30 lines
  • verify_invoice_number reads unknown 15h ago

    適格請求書発行事業者番号（T＋13桁）の登録・取消・失効を日付付きで照合します。本サービスは法人・人格のない社団等のデータのみを取り込み、個人事業者のデータを取り込んでいないため、個人事業者の番号はここでは見つかりません（公表サイト https://www.invoice-kohyo.nta.go.jp/ では確認できる場合があります）。未発見を無効・不存在と断定しません。登録ありの応答には法人番号データ由来の法人名 name・所在地 address を含みます（法人番号表に無い場合は null。未発見の応答は name/address ともに null）。入力例: {"invoiceNumber": "T1180301018771"}

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "invoiceNumber"
  ],
  "properties": {
    "invoiceNumber": {
      "type": "string",
      "description": "T＋13桁の登録番号。例: \"T1180301018771\""
    }
  }
}
    arguments 13 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 ec8a9a5952b409df.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ec8a9a5952b409df/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/ec8a9a5952b409df/badge.svg)](https://brick.blue/agent/ec8a9a5952b409df?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
100%

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.

_ also on plugrail.dev 2 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.