PlugRail Corporate Number
REMOTE · JP-CORPORATE.PLUGRAIL.DEV · SCANNED SEP 27
Japanese corporate number lookup using official National Tax Agency public data.
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 886 tokens (~147/item across 6 items; 6 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 Management10
- Stability observed for 3 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the PlugRail Corporate Number MCP server?
PlugRail Corporate Number is a hosted endpoint at https://jp-corporate.plugrail.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 · jp-corporate.plugrail.dev
claude mcp add --transport http dev-plugrail-jp-corporate 'https://jp-corporate.plugrail.dev/mcp'
{
"mcpServers": {
"dev-plugrail-jp-corporate": {
"url": "https://jp-corporate.plugrail.dev/mcp"
}
}
} {
"servers": {
"dev-plugrail-jp-corporate": {
"type": "http",
"url": "https://jp-corporate.plugrail.dev/mcp"
}
}
} [mcp_servers.dev-plugrail-jp-corporate] url = "https://jp-corporate.plugrail.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-plugrail-jp-corporate": {
"type": "remote",
"url": "https://jp-corporate.plugrail.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-plugrail-jp-corporate --url 'https://jp-corporate.plugrail.dev/mcp' --transport streamable-http
mcp_servers:
dev-plugrail-jp-corporate:
url: "https://jp-corporate.plugrail.dev/mcp" {
"McpServers": {
"dev-plugrail-jp-corporate": {
"Transport": "http",
"Url": "https://jp-corporate.plugrail.dev/mcp"
}
}
} assistant mcp add dev-plugrail-jp-corporate -t streamable-http -u 'https://jp-corporate.plugrail.dev/mcp'
{
"mcpServers": {
"dev-plugrail-jp-corporate": {
"type": "http",
"url": "https://jp-corporate.plugrail.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 60
First indexed and scored.
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 27 Sept 2026 · Probed https://jp-corporate.plugrail.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=plugrail.dev | CN=WE1,O=Google Trust Services,C=US | 16 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | b2b080294003ab590ecf7a3bfc1d59a1 |
| SANs: plugrail.dev, jp-corporate.plugrail.dev, *.jp-corporate.plugrail.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 jp-corporate.plugrail.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| plugrail.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://jp-corporate.plugrail.dev/mcp | Verified | 200 | |
| http (plaintext) | http://jp-corporate.plugrail.dev/mcp | Inconclusive | 405 |
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 →
company_profile ~114
法人番号（13桁）で基本情報・補助金・届出・財務の会社プロファイルを返す。各領域の出典・鮮度・欠損を保持し、部分障害時は取得済みと欠損を同時に返す。入力例: {"corporateNumber": "8000000000001"}
| Name | Type | Req | Description |
|---|---|---|---|
| corporateNumber | string | yes | 13桁の法人番号。例: "8000000000001" |
No output schema declared.
No examples provided.
lookup_corporate ~253
法人番号の確定照会と名称・所在地の候補探索を分離して返す。名称だけでは断定せず複数候補と根拠別scoreを返す。番号確定例: {"corporateNumber": "8000000000001"}／候補例: {"name": "渋谷", "prefecture": "13", "limit": 10}
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | 所在地の絞込語（候補探索の任意）。例: "渋谷" |
| corporateNumber | string | – | 13桁の法人番号（確定照会）。例: "8000000000001" |
| cursor | string | – | 前回応答の nextCursor（透過・省略可）。 |
| limit | integer | – | 取得件数 1〜20（省略時は10） |
| name | string | – | 法人名の検索語（候補探索）。例: "渋谷" |
| prefecture | string | – | 都道府県コード2桁（候補探索は必須）。例: "13"（東京） |
No output schema declared.
No examples provided.
search_corporate_by_address ~162
都道府県＋所在地の接頭辞で日本の法人を検索します。国税庁公開データに基づきます。入力例: {"prefecture": "13", "prefix": "渋谷", "limit": 10}
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | 前回応答の nextCursor（透過・省略可）。 |
| limit | integer | – | 取得件数 1〜20（省略時は10）。例: 10 |
| prefecture | string | yes | 都道府県コード2桁。例: "13"（東京） |
| prefix | string | yes | 検索接頭辞（非空）。例: "渋谷" |
No output schema declared.
No examples provided.
search_corporate_by_name ~163
都道府県＋法人名の接頭辞で日本の法人を検索します。国税庁公開データに基づきます。入力例: {"prefecture": "13", "prefix": "渋谷", "limit": 10}
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | 前回応答の nextCursor（透過・省略可）。 |
| limit | integer | – | 取得件数 1〜20（省略時は10）。例: 10 |
| prefecture | string | yes | 都道府県コード2桁。例: "13"（東京） |
| prefix | string | yes | 検索接頭辞（非空）。例: "渋谷" |
No output schema declared.
No examples provided.
search_corporate_by_number ~82
法人番号（13桁）で日本の法人を1件検索します。国税庁公開データに基づきます。入力例: {"corporateNumber": "8000000000001"}
| Name | Type | Req | Description |
|---|---|---|---|
| corporateNumber | string | yes | 13桁の法人番号。例: "8000000000001" |
No output schema declared.
No examples provided.
verify_invoice_number ~112
適格請求書発行事業者番号（T＋13桁）の登録・取消・失効を日付付きで照合します。未発見は個人非掲載または未収録として明示し、無効・不存在と断定しません。入力例: {"invoiceNumber": "T8000000000001"}
| Name | Type | Req | Description |
|---|---|---|---|
| invoiceNumber | string | yes | T＋13桁の登録番号。例: "T8000000000001" |
No output schema declared.
No examples provided.
What is the PlugRail Corporate Number MCP server?
PlugRail Corporate Number is an MCP server listed in the public MCP registry as dev.plugrail/jp-corporate. Japanese corporate number lookup using official National Tax Agency public data. This page covers its hosted endpoint (https://jp-corporate.plugrail.dev/mcp).
Is the PlugRail Corporate Number MCP server safe to use?
PlugRail Corporate Number scores 61 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 PlugRail Corporate Number MCP server expose?
PlugRail Corporate Number exposes 6 tools: search_corporate_by_number, search_corporate_by_name, search_corporate_by_address, lookup_corporate, verify_invoice_number, company_profile. Their descriptions and schemas cost roughly 886 tokens of context every time the server is loaded.
Does the PlugRail Corporate Number MCP server require authentication?
No. We connected to PlugRail Corporate Number without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PlugRail Corporate Number MCP server still maintained?
PlugRail Corporate Number is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.