PlugRail JP Corporate
REMOTE · JP-CORPORATE.PLUGRAIL.DEV · SCANNED OCT 15
Search Japanese corporations and verify invoice numbers using official National Tax Agency 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1250 tokens (~208/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 Management70
- Stability observed for 21 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 JP Corporate MCP server?
PlugRail JP Corporate 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.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 60. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 50. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 0
- Tool “company_profile” rewrote its description, which is the text the model reads security
- Tool “lookup_corporate” rewrote its description, which is the text the model reads security
- Tool “search_corporate_by_address” rewrote its description, which is the text the model reads security
- Tool “search_corporate_by_number” rewrote its description, which is the text the model reads security
- Tool “verify_invoice_number” rewrote its description, which is the text the model reads security
- Schema quality: 178 → 208 ▼ functional
- “company_profile” reworded the description of “corporateNumber” cosmetic
- “lookup_corporate” reworded the description of “corporateNumber” cosmetic
- “search_corporate_by_number” reworded the description of “corporateNumber” cosmetic
- “verify_invoice_number” reworded the description of “invoiceNumber” cosmetic
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 40. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Schema Quality & AI Usability fell 1.
- 3 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.
- 1 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.
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 15 Oct 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": "1180301018771"}
| Name | Type | Req | Description |
|---|---|---|---|
| corporateNumber | string | yes | 13桁の法人番号。例: "1180301018771" |
No output schema declared.
No examples provided.
lookup_corporate ~439
法人番号の確定照会と名称・所在地の候補探索を分離して返す。名称だけでは断定せず複数候補と根拠別scoreを返す。候補探索は name 指定時は prefecture 任意（省略時は全国前方一致で searchedNationwide:true・候補に県コード付き・県か住所を足すと絞り込める）。prefecture は '13' または '東京都' のどちらでも可。address が「東京都渋谷区…」のように都道府県名で始まれば prefecture は省略可（推定）。address のみの検索は prefecture または推定が必須（全国非対応）。番号確定例: {"corporateNumber": "1180301018771"}／候補例: {"name": "渋谷", "prefecture": "13", "limit": 10}／全国例: {"name": "山田工業"}
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | 所在地の絞込語（候補探索の任意）。例: "渋谷" |
| corporateNumber | string | – | 13桁の法人番号（確定照会）。例: "1180301018771" |
| cursor | string | – | 前回応答の nextCursor（透過・省略可）。 |
| limit | integer | – | 取得件数 1〜20（省略時は10） |
| name | string | – | 法人名の検索語（候補探索）。例: "渋谷" |
| prefecture | – | – | 都道府県（name 指定時は任意・省略時は全国検索。address のみのときは必須。address 先頭の都道府県名から推定できれば省略可）。JISコード "13"・13・"1" または都道府県名 "東京都"・"東京" のどちらでも可 |
No output schema declared.
No examples provided.
search_corporate_by_address ~232
都道府県＋所在地の接頭辞で日本の法人を検索します。国税庁公開データに基づきます。市区町村名の前方一致が主経路で、町名以降を含む指定（例: 港区港南・東京都港区港南）は住所全文の前方一致へ迂回し、町名のみの断片（例: 港南）は住所全文の部分一致で拾います。入力例: {"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": "1180301018771"}
| Name | Type | Req | Description |
|---|---|---|---|
| corporateNumber | string | yes | 13桁の法人番号。例: "1180301018771" |
No output schema declared.
No examples provided.
verify_invoice_number ~220
適格請求書発行事業者番号（T＋13桁）の登録・取消・失効を日付付きで照合します。本サービスは法人・人格のない社団等のデータのみを取り込み、個人事業者のデータを取り込んでいないため、個人事業者の番号はここでは見つかりません（公表サイト https://www.invoice-kohyo.nta.go.jp/ では確認できる場合があります）。未発見を無効・不存在と断定しません。登録ありの応答には法人番号データ由来の法人名 name・所在地 address を含みます（法人番号表に無い場合は null。未発見の応答は name/address ともに null）。入力例: {"invoiceNumber": "T1180301018771"}
| Name | Type | Req | Description |
|---|---|---|---|
| invoiceNumber | string | yes | T＋13桁の登録番号。例: "T1180301018771" |
No output schema declared.
No examples provided.
What is the PlugRail JP Corporate MCP server?
PlugRail JP Corporate is an MCP server listed in the public MCP registry as dev.plugrail/jp-corporate. Search Japanese corporations and verify invoice numbers using official National Tax Agency data. This page covers its hosted endpoint (https://jp-corporate.plugrail.dev/mcp).
Is the PlugRail JP Corporate MCP server safe to use?
PlugRail JP Corporate scores 69 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 JP Corporate MCP server expose?
PlugRail JP Corporate 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 1,250 tokens of context every time the server is loaded.
Does the PlugRail JP Corporate MCP server require authentication?
No. We connected to PlugRail JP Corporate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PlugRail JP Corporate MCP server still maintained?
PlugRail JP Corporate is still listed as active in the MCP registry. We last reached this channel on 15 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.