Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Japan Public Data (法人番号・登録支援機関・官公需入札)

REMOTE · MCP-TOOLS.TAKARA0408103123.WORKERS.DEV

Japan public data: corporate numbers, registered support organizations, government bid notices.

+4 this week 72 Trust /100

Last scanned (20 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 654 tokens (~218/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 22 Oct 26 66

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://mcp-tools.takara0408103123.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=takara0408103123.workers.dev CN=WE1,O=Google Trust Services,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA256 a6ff36c5b5686131139af6c9d05b4853
SANs: takara0408103123.workers.dev, *.takara0408103123.workers.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp-tools.takara0408103123.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp-tools.takara0408103123.workers.dev/mcp Verified 200
http (plaintext) http://mcp-tools.takara0408103123.workers.dev/mcp Inconclusive 405
MCP tools · 3 exposed · ~654 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
lookup_corporate_number ~145

Look up Japanese companies in the National Tax Agency Corporate Number Publication Site. Search by 13-digit corporate number, or by company name. Returns name, address and status. 国税庁 法人番号公表サイトから、法人番号(13桁)または法人名で法人情報(名称・所在地・閉鎖有無)を検索します。

NameTypeReqDescription
namestring–Company name, partial match, closed companies excluded / 法人名(部分一致・閉鎖法人は対象外)。number とは同時指定不可
numberstring–13-digit corporate number / 法人番号(13桁)

No output schema declared.

No examples provided.

search_local_govt_bids ~259

Search bid and tender notices from Japanese local governments and national agencies via the KKJ (官公需情報ポータルサイト) search API by the Small and Medium Enterprise Agency. Filter by keywords (AND), prefecture, issuing organization and notice date. Returns title, organization, dates and the notice URL. 官公需情報ポータルサイトの検索APIで、自治体・国の機関の入札・公募情報をキーワード・都道府県・機関名・公告日で検索します。

NameTypeReqDescription
limitinteger–Max results (default 10, max 20) / 最大件数
organizationstring–Issuing organization, partial match / 機関名(部分一致。例:横浜市)
prefecturestring–Prefecture name / 都道府県(例:東京都、大阪)
querystring–Keywords separated by spaces (AND) / キーワード(空白区切りでAND)
sincestring–Notices issued on or after this date, YYYY-MM-DD (default: 30 days ago) / 公告日がこの日以降(既定:30日前)

No output schema declared.

No examples provided.

search_support_orgs ~250

Search the Immigration Services Agency of Japan registry of Registered Support Organizations for Specified Skilled Workers. Filter by name, location (prefecture/city in head office or support office address) and supported language. Organizations that reported suspension are excluded unless includeSuspended is true. 出入国在留管理庁「登録支援機関登録簿」から、特定技能外国人の登録支援機関を名称・所在地・対応言語で検索します(同梱データ・基準日あり)。

NameTypeReqDescription
includeSuspendedboolean–Include organizations that reported suspension / 支援業務休止の届出がある機関も含める
languagestring–Supported language in Japanese / 対応言語(例:ベトナム語、英語)
limitinteger–Max results (default 10, max 20) / 最大件数
locationstring–Prefecture or city, partial match on address / 所在地(例:東京都、横浜市。住所の部分一致)
namestring–Organization name, partial match / 名称(部分一致)

No output schema declared.

No examples provided.

Install

How do I install the Japan Public Data (法人番号・登録支援機関・官公需入札) MCP server?

Japan Public Data (法人番号・登録支援機関・官公需入札) is a hosted endpoint at https://mcp-tools.takara0408103123.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp-tools.takara0408103123.workers.dev

# add to Claude Code
claude mcp add --transport http takaratomita-mcp-tools 'https://mcp-tools.takara0408103123.workers.dev/mcp'
Common questions

What is the Japan Public Data (法人番号・登録支援機関・官公需入札) MCP server?

Japan Public Data (法人番号・登録支援機関・官公需入札) is an MCP server listed in the public MCP registry as io.github.takaratomita/mcp-tools. Japan public data: corporate numbers, registered support organizations, government bid notices. This page covers its hosted endpoint (https://mcp-tools.takara0408103123.workers.dev/mcp).

Is the Japan Public Data (法人番号・登録支援機関・官公需入札) MCP server safe to use?

Japan Public Data (法人番号・登録支援機関・官公需入札) scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Japan Public Data (法人番号・登録支援機関・官公需入札) MCP server expose?

Japan Public Data (法人番号・登録支援機関・官公需入札) exposes 3 tools: lookup_corporate_number, search_support_orgs, search_local_govt_bids. Their descriptions and schemas cost roughly 654 tokens of context every time the server is loaded.

Does the Japan Public Data (法人番号・登録支援機関・官公需入札) MCP server require authentication?

No. We connected to Japan Public Data (法人番号・登録支援機関・官公需入札) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Japan Public Data (法人番号・登録支援機関・官公需入札) MCP server still maintained?

Japan Public Data (法人番号・登録支援機関・官公需入札) is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.