PlugRail JP Corporate
REMOTE · JP-CORPORATE.PLUGRAIL.DEV
Search Japanese corporations and verify invoice numbers using official National Tax Agency data.
Available components
Last scanned (16 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2313 tokens (~330/item across 7 items; 7 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 9 Nov 26 +6
- Authorization: unverified → partial ▲ security
- Tool “company_profile” rewrote its description, which is the text the model reads security
- Tool “search_corporate_by_name” 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 “search_invoice_batch” rewrote its description, which is the text the model reads security
- Schema quality: 209 → 330 ▼ functional
- “company_profile” reworded the description of “corporateNumber” cosmetic
- “search_corporate_by_address” reworded the description of “cursor” cosmetic
- “search_corporate_by_address” reworded the description of “prefecture” cosmetic
- “search_corporate_by_address” reworded the description of “prefix” cosmetic
- “search_corporate_by_name” reworded the description of “cursor” cosmetic
- “search_corporate_by_name” reworded the description of “prefecture” cosmetic
- “search_corporate_by_name” reworded the description of “prefix” cosmetic
- “search_corporate_by_number” reworded the description of “corporateNumber” cosmetic
- “search_invoice_batch” reworded the description of “invoiceNumbers” cosmetic
- 8 Nov 26 0
- Stability: 0.97 → pass security
- 7 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Nov 26 0
- Tool “lookup_corporate” rewrote its description, which is the text the model reads security
- Schema quality: 1250 → 1467 ▼ functional
- New tool “search_invoice_batch” functional
- 24 Oct 26 0
- Stability: 0.97 → pass security
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 21 Nov 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 | 15 Nov 2026 | 13 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 33b01bf90c25f1110eac110735d07d9f |
| 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. | DS published | 60074 | 8 | Verified |
| plugrail.dev. | No DS | 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 ~266
法人番号(ハイフンなし13桁)を確定キーに、法人番号公表・インボイス(国税庁公表データ)と gBizINFO の4領域(基本情報・補助金・届出・財務)を1件にまとめて返します。領域ごとに出典・取得日時・欠損理由を付け、一部の領域だけ取得できたときは取得済みと欠損を同時に返します(全領域が欠損のときは not_found)。名称だけでは統合しません。gBizINFO の4領域は pro プランのみ。鍵なし・free プランは法人番号公表とインボイスだけを返し、gBizINFO の領域は欠損(pro_required)になります。鍵なし・free プランは暦月100回まで、pro プランは無制限です。入力例: {"corporateNumber": "1180301018771"}
| Name | Type | Req | Description |
|---|---|---|---|
| corporateNumber | string | yes | ハイフンなしの13桁の法人番号。形式が違うと invalid_input。例: "1180301018771" |
No output schema declared.
No examples provided.
lookup_corporate ~481
法人番号の確定照会と名称・所在地の候補探索を分離して返す。名称だけでは断定せず複数候補と根拠別scoreを返す。候補探索は name 指定時は prefecture 任意(省略時は全国前方一致で searchedNationwide:true・候補に県コード付き・県か住所を足すと絞り込める)。prefecture は '13' または '東京都' のどちらでも可。address が「東京都渋谷区…」のように都道府県名で始まれば prefecture は省略可(推定)。address のみの検索は prefecture または推定が必須(全国非対応)。番号確定例: {"corporateNumber": "1180301018771"}/候補例: {"name": "渋谷", "prefecture": "13", "limit": 10}/全国例: {"name": "山田工業"}corporateNumber はハイフンなし13桁の文字列(数値・ハイフン付き・先頭 T 付きは不可)。番号と 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 ~276
都道府県+所在地の接頭辞で日本の法人を検索します。国税庁公開データに基づきます。市区町村名の前方一致が主経路で、町名以降を含む指定(例: 港区港南・東京都港区港南)は住所全文の前方一致へ迂回し、町名のみの断片(例: 港南)は住所全文の部分一致で拾います。入力例: {"prefecture": "13", "prefix": "渋谷", "limit": 10}
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | 前回応答の nextCursor をそのまま渡す(自作・改変した値は invalid_input)。 |
| limit | integer | – | 取得件数 1〜20(省略時は10)。例: 10 |
| prefecture | string | yes | 都道府県コード2桁(JIS X 0401。都道府県名は不可)。例: "13"(東京) |
| prefix | string | yes | 検索接頭辞(非空。全角・半角などの表記揺れは揃えて照合)。例: "渋谷" |
No output schema declared.
No examples provided.
search_corporate_by_name ~455
都道府県コードと法人名の前方一致(接頭辞)で日本の法人を検索し、候補の法人番号・名称・所在地・存続状態を返します(国税庁「法人番号公表サイト」の公開データを加工)。法人番号が分からず名称から探すときに使います。番号が分かれば search_corporate_by_number、名称と所在地から番号の確定まで行うなら lookup_corporate を使います。部分一致・曖昧一致はしません(「渋谷」は名称が「渋谷」で始まる法人だけが対象)。入力の法人格(株式会社など)は除いて照合し、旧字・新字の字体違いは両方検索します。返り値は candidates(limit 件まで。0件は「該当なし」であり「存在しない」との断定ではありません)、nextCursor(続きがあるときだけ。字体違いを展開した先頭ページでは返りません)、generation(取り込み世代)、出典。対象は法人番号を持つ法人のみで、個人事業者は含みません。鍵なし・free プランは暦月100回まで、pro プランは無制限です。入力例: {"prefecture": "13", "prefix": "渋谷", "limit": 10}
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | 前回応答の nextCursor をそのまま渡す(自作・改変した値は invalid_input)。 |
| limit | integer | – | 取得件数 1〜20(省略時は10)。例: 10 |
| prefecture | string | yes | 都道府県コード2桁(JIS X 0401。都道府県名は不可)。例: "13"(東京) |
| prefix | string | yes | 検索接頭辞(非空。全角・半角などの表記揺れは揃えて照合)。例: "渋谷" |
No output schema declared.
No examples provided.
search_corporate_by_number ~267
法人番号(ハイフンなし13桁)で日本の法人を1件検索し、法人番号・名称・所在地・存続状態を返します(国税庁「法人番号公表サイト」の公開データを加工)。番号が分かっているときに使い、名称や所在地しか分からないときは search_corporate_by_name/search_corporate_by_address か lookup_corporate を使います。返り値は candidates(該当は1件まで。status は active=存続・closed=閉鎖)、generation(取り込み世代)、出典。該当なしは candidates が空配列です。検査用数字が合わない番号は invalid_input で返ります(検索前に弾くため上限カウントにも入りません)。鍵なし・free プランは暦月100回まで、pro プランは無制限です。入力例: {"corporateNumber": "1180301018771"}
| Name | Type | Req | Description |
|---|---|---|---|
| corporateNumber | string | yes | ハイフンなしの13桁の法人番号(検査用数字つき)。例: "1180301018771" |
No output schema declared.
No examples provided.
search_invoice_batch ~348
適格請求書発行事業者番号(T+13桁)を1回の呼び出しで最大100件まで一括照会し、番号ごとに status(active=登録・cancelled=取消・expired=失効・not_found=未登録)と登録日・取消日・失効日を返します(国税庁公表データを加工)。results は入力順に1対1で返し、重複は除去しません。summary は出現回数で数えます。not_found は「その番号が存在しない」との断定ではなく、取り込みデータに無いことを示します(個人事業者の番号は取り込んでいないため、ここでは見つかりません)。形式が合わない番号(半角の T+13桁の数字でないもの)が1件でもあると、照会せず全体を拒否します。空配列と101件以上も拒否します。鍵なし・free プランは暦月100回まで(1回の呼び出しを1回として数えます)、pro プランは無制限です。入力例: {"invoiceNumbers": ["T1180301018771", "T1180301018772"]}
| Name | Type | Req | Description |
|---|---|---|---|
| invoiceNumbers | array | yes | 半角の T+13桁の適格請求書発行事業者番号の配列(1〜100件・入力順に結果を返す)。例: ["T1180301018771"] |
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.
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'
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 79 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 7 tools: search_corporate_by_number, search_corporate_by_name, search_corporate_by_address, lookup_corporate, verify_invoice_number, and 2 more. Their descriptions and schemas cost roughly 2,313 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the PlugRail JP Corporate MCP server?
VerifyMCP ran 12 checks on PlugRail JP Corporate, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about PlugRail JP Corporate: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.