Skip to content

PlugRail JP Corporate MCP server

dev.plugrail/jp-corporateplugrail.devstreamable-httpv0.1.1Scanned

Search Japanese corporations and verify invoice numbers using official National Tax Agency data.

7 tools: 2 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 2 write, 5 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the PlugRail JP Corporate MCP server can do

The PlugRail JP Corporate MCP server is published by plugrail.dev, a domain the MCP Registry verified. It has 7 tools. It can create or change data (2 tools: verify_invoice_number and company_profile), but cannot delete data. 5 tools only read.

1 tool brings in text other people can write (company_profile).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 11, 2026, version 0.1.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 2Claude Code: ask
  • company_profile法人番号(ハイフンなし13桁)を確定キーに、法人番号公表・インボイス(国税庁公表データ)と gBizINFO の4領域(基本情報・補助金・届出・財務)を1件にまとめて返します。領域ごとに出典・取得日時・欠損理由を付け、一部の領域だけ取得できたときは取得済みと欠損を同時に返します(全領域が欠損のときは not_found)。名称だけでは統合しません。gBizI…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    法人番号(ハイフンなし13桁)を確定キーに、法人番号公表・インボイス(国税庁公表データ)と gBizINFO の4領域(基本情報・補助金・届出・財務)を1件にまとめて返します。領域ごとに出典・取得日時・欠損理由を付け、一部の領域だけ取得できたときは取得済みと欠損を同時に返します(全領域が欠損のときは not_found)。名称だけでは統合しません。gBizINFO の4領域は pro プランのみ。鍵なし・free プランは法人番号公表とインボイスだけを返し、gBizINFO の領域は欠損(pro_required)になります。鍵なし・free プランは暦月100回まで、pro プランは無制限です。入力例: {"corporateNumber": "1180301018771"}

    Annotations the server declares

    • title: 法人番号で会社プロファイルを取得
    • readOnlyHint: true
    • openWorldHint: true
  • verify_invoice_number適格請求書発行事業者番号(T+13桁)の登録・取消・失効を日付付きで照合します。本サービスは法人・人格のない社団等のデータのみを取り込み、個人事業者のデータを取り込んでいないため、個人事業者の番号はここでは見つかりません(公表サイト https://www.invoice-kohyo.nta.go.jp/ では確認できる場合があります)。未発見を無効・不存在…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    適格請求書発行事業者番号(T+13桁)の登録・取消・失効を日付付きで照合します。本サービスは法人・人格のない社団等のデータのみを取り込み、個人事業者のデータを取り込んでいないため、個人事業者の番号はここでは見つかりません(公表サイト https://www.invoice-kohyo.nta.go.jp/ では確認できる場合があります)。未発見を無効・不存在と断定しません。登録ありの応答には法人番号データ由来の法人名 name・所在地 address を含みます(法人番号表に無い場合は null。未発見の応答は name/address ともに null)。入力例: {"invoiceNumber": "T1180301018771"}

    Annotations the server declares

    • title: インボイス番号を照合
    • readOnlyHint: true
    • openWorldHint: false
Only reads 5Show 5 read-only tools
  • lookup_corporate法人番号の確定照会と名称・所在地の候補探索を分離して返す。名称だけでは断定せず複数候補と根拠別scoreを返す。候補探索は name 指定時は prefecture 任意(省略時は全国前方一致で searchedNationwide:true・候補に県コード付き・県か住所を足すと絞り込める)。prefecture は '13' または '東京都' のどちらで…No findings

    Why it is in this group

    • The name "lookup_corporate" says "lookup": a word for reading.
    Description, as the server wrote it
    法人番号の確定照会と名称・所在地の候補探索を分離して返す。名称だけでは断定せず複数候補と根拠別scoreを返す。候補探索は name 指定時は prefecture 任意(省略時は全国前方一致で searchedNationwide:true・候補に県コード付き・県か住所を足すと絞り込める)。prefecture は '13' または '東京都' のどちらでも可。address が「東京都渋谷区…」のように都道府県名で始まれば prefecture は省略可(推定)。address のみの検索は prefecture または推定が必須(全国非対応)。番号確定例: {"corporateNumber": "1180301018771"}/候補例: {"name": "渋谷", "prefecture": "13", "limit": 10}/全国例: {"name": "山田工業"}corporateNumber はハイフンなし13桁の文字列(数値・ハイフン付き・先頭 T 付きは不可)。番号と name は併用不可。

    Annotations the server declares

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

    Why it is in this group

    • The name "search_corporate_by_address" says "search": a word for reading.
    Description, as the server wrote it
    都道府県+所在地の接頭辞で日本の法人を検索します。国税庁公開データに基づきます。市区町村名の前方一致が主経路で、町名以降を含む指定(例: 港区港南・東京都港区港南)は住所全文の前方一致へ迂回し、町名のみの断片(例: 港南)は住所全文の部分一致で拾います。入力例: {"prefecture": "13", "prefix": "渋谷", "limit": 10}

    Annotations the server declares

    • title: 都道府県と所在地で法人を検索
    • readOnlyHint: true
    • openWorldHint: false
  • search_corporate_by_name都道府県コードと法人名の前方一致(接頭辞)で日本の法人を検索し、候補の法人番号・名称・所在地・存続状態を返します(国税庁「法人番号公表サイト」の公開データを加工)。法人番号が分からず名称から探すときに使います。番号が分かれば search_corporate_by_number、名称と所在地から番号の確定まで行うなら lookup_corporate を使い…No findings

    Why it is in this group

    • The name "search_corporate_by_name" says "search": a word for reading.
    Description, as the server wrote it
    都道府県コードと法人名の前方一致(接頭辞)で日本の法人を検索し、候補の法人番号・名称・所在地・存続状態を返します(国税庁「法人番号公表サイト」の公開データを加工)。法人番号が分からず名称から探すときに使います。番号が分かれば search_corporate_by_number、名称と所在地から番号の確定まで行うなら lookup_corporate を使います。部分一致・曖昧一致はしません(「渋谷」は名称が「渋谷」で始まる法人だけが対象)。入力の法人格(株式会社など)は除いて照合し、旧字・新字の字体違いは両方検索します。返り値は candidates(limit 件まで。0件は「該当なし」であり「存在しない」との断定ではありません)、nextCursor(続きがあるときだけ。字体違いを展開した先頭ページでは返りません)、generation(取り込み世代)、出典。対象は法人番号を持つ法人のみで、個人事業者は含みません。鍵なし・free プランは暦月100回まで、pro プランは無制限です。入力例: {"prefecture": "13", "prefix": "渋谷", "limit": 10}

    Annotations the server declares

    • title: 都道府県と名称で法人を検索
    • readOnlyHint: true
    • openWorldHint: false
  • search_corporate_by_number法人番号(ハイフンなし13桁)で日本の法人を1件検索し、法人番号・名称・所在地・存続状態を返します(国税庁「法人番号公表サイト」の公開データを加工)。番号が分かっているときに使い、名称や所在地しか分からないときは search_corporate_by_name/search_corporate_by_address か lookup_corporate を…No findings

    Why it is in this group

    • The name "search_corporate_by_number" says "search": a word for reading.
    Description, as the server wrote it
    法人番号(ハイフンなし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"}

    Annotations the server declares

    • title: 法人番号で法人を検索
    • readOnlyHint: true
    • openWorldHint: false
  • search_invoice_batch適格請求書発行事業者番号(T+13桁)を1回の呼び出しで最大100件まで一括照会し、番号ごとに status(active=登録・cancelled=取消・expired=失効・not_found=未登録)と登録日・取消日・失効日を返します(国税庁公表データを加工)。results は入力順に1対1で返し、重複は除去しません。summary は出現回数で数え…No findings

    Why it is in this group

    • The name "search_invoice_batch" says "search": a word for reading.
    Description, as the server wrote it
    適格請求書発行事業者番号(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"]}

    Annotations the server declares

    • title: インボイス番号を一括照会
    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:52 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://jp-corporate.plugrail.dev/.well-known/oauth-protected-resource/mcp
Authorization servers
https://api.descope.com/v1/apps/agentic/P3JDYOMs4GLg0s3Zb26zp4RARA0j/RS3JDb1RbBrEmoZI7dxlb3esEhKVB
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://jp-corporate.plugrail.dev/mcp: tools/list returned 7 tools to an anonymous client, including verify_invoice_number (write), company_profile (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added, 6 changed.+1 added~6 changedView diff

Install

Pinned to version 0.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http jp-corporate https://jp-corporate.plugrail.dev/mcp
claude mcp add --transport http jp-corporate https://jp-corporate.plugrail.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__jp-corporate__search_corporate_by_number",
      "mcp__jp-corporate__search_corporate_by_name",
      "mcp__jp-corporate__search_corporate_by_address",
      "mcp__jp-corporate__lookup_corporate",
      "mcp__jp-corporate__search_invoice_batch"
    ],
    "ask": [
      "mcp__jp-corporate__verify_invoice_number",
      "mcp__jp-corporate__company_profile"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as jp-corporate. Review it before you use it.

Capability tags behind 1 rule
  • mcp__jp-corporate__company_profile untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.plugrail/jp-corporate/verify?hash=b8cd26711cde58bae749cf4ae2000afbf304fc89a73f7217cf340e742dcab880" | jq -e '.changed == false'

Pinned hash b8cd26711cde, from Nov 11, 2026, 09:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.plugrail/jp-corporate/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.plugrail/jp-corporate
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.plugrail/jp-corporate.svg)](https://radar.anlyon.com/servers/dev.plugrail/jp-corporate)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:12 UTC.

PlugRail JP Corporate MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the PlugRail JP Corporate MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the PlugRail JP Corporate MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the PlugRail JP Corporate MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the PlugRail JP Corporate MCP server have?

7 tools: 2 write, 5 read. verify_invoice_number, company_profile, search_corporate_by_number, search_corporate_by_name, search_corporate_by_address, lookup_corporate and search_invoice_batch.

Does the PlugRail JP Corporate MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the PlugRail JP Corporate MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the PlugRail JP Corporate MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.