# PlugRail Corporate Number (remote · jp-corporate.plugrail.dev)

Japanese corporate number lookup using official National Tax Agency public data.

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `jp-corporate.plugrail.dev`: 61/100 (this document), [markdown](https://verifymcp.io/servers/dev-plugrail-jp-corporate/jp-corporate.md), [page](https://verifymcp.io/servers/dev-plugrail-jp-corporate/jp-corporate)

## Channel facts

- Endpoint: `https://jp-corporate.plugrail.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-27.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "dev-plugrail-jp-corporate": {
      "url": "https://jp-corporate.plugrail.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-plugrail-jp-corporate": {
      "type": "http",
      "url": "https://jp-corporate.plugrail.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-plugrail-jp-corporate]
url = "https://jp-corporate.plugrail.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-plugrail-jp-corporate": {
      "type": "remote",
      "url": "https://jp-corporate.plugrail.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-plugrail-jp-corporate --url 'https://jp-corporate.plugrail.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-plugrail-jp-corporate:
    url: "https://jp-corporate.plugrail.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-plugrail-jp-corporate": {
      "Transport": "http",
      "Url": "https://jp-corporate.plugrail.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-plugrail-jp-corporate -t streamable-http -u 'https://jp-corporate.plugrail.dev/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 61, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 60)

First indexed and scored.

## MCP tools (6)

### `search_corporate_by_number` (~82 tokens)

法人番号（13桁）で日本の法人を1件検索します。国税庁公開データに基づきます。入力例: {"corporateNumber": "8000000000001"}

Input parameters:

- `corporateNumber` (string, required): 13桁の法人番号。例: "8000000000001"

### `search_corporate_by_name` (~163 tokens)

都道府県＋法人名の接頭辞で日本の法人を検索します。国税庁公開データに基づきます。入力例: {"prefecture": "13", "prefix": "渋谷", "limit": 10}

Input parameters:

- `cursor` (string): 前回応答の nextCursor（透過・省略可）。
- `limit` (integer): 取得件数 1〜20（省略時は10）。例: 10
- `prefecture` (string, required): 都道府県コード2桁。例: "13"（東京）
- `prefix` (string, required): 検索接頭辞（非空）。例: "渋谷"

### `search_corporate_by_address` (~162 tokens)

都道府県＋所在地の接頭辞で日本の法人を検索します。国税庁公開データに基づきます。入力例: {"prefecture": "13", "prefix": "渋谷", "limit": 10}

Input parameters:

- `cursor` (string): 前回応答の nextCursor（透過・省略可）。
- `limit` (integer): 取得件数 1〜20（省略時は10）。例: 10
- `prefecture` (string, required): 都道府県コード2桁。例: "13"（東京）
- `prefix` (string, required): 検索接頭辞（非空）。例: "渋谷"

### `lookup_corporate` (~253 tokens)

法人番号の確定照会と名称・所在地の候補探索を分離して返す。名称だけでは断定せず複数候補と根拠別scoreを返す。番号確定例: {"corporateNumber": "8000000000001"}／候補例: {"name": "渋谷", "prefecture": "13", "limit": 10}

Input parameters:

- `address` (string): 所在地の絞込語（候補探索の任意）。例: "渋谷"
- `corporateNumber` (string): 13桁の法人番号（確定照会）。例: "8000000000001"
- `cursor` (string): 前回応答の nextCursor（透過・省略可）。
- `limit` (integer): 取得件数 1〜20（省略時は10）
- `name` (string): 法人名の検索語（候補探索）。例: "渋谷"
- `prefecture` (string): 都道府県コード2桁（候補探索は必須）。例: "13"（東京）

### `verify_invoice_number` (~112 tokens)

適格請求書発行事業者番号（T＋13桁）の登録・取消・失効を日付付きで照合します。未発見は個人非掲載または未収録として明示し、無効・不存在と断定しません。入力例: {"invoiceNumber": "T8000000000001"}

Input parameters:

- `invoiceNumber` (string, required): T＋13桁の登録番号。例: "T8000000000001"

### `company_profile` (~114 tokens)

法人番号（13桁）で基本情報・補助金・届出・財務の会社プロファイルを返す。各領域の出典・鮮度・欠損を保持し、部分障害時は取得済みと欠損を同時に返す。入力例: {"corporateNumber": "8000000000001"}

Input parameters:

- `corporateNumber` (string, required): 13桁の法人番号。例: "8000000000001"

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-plugrail-jp-corporate/jp-corporate#diagnostics

## Score history

- 2026-09-27: 61
- 2026-09-26: 61
- 2026-09-25: 61
- 2026-09-24: 60

## Common questions

### 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.

## Links

- Remote endpoint: https://jp-corporate.plugrail.dev/mcp
- Repository: https://github.com/plugrail/servers
- Website: https://plugrail.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-plugrail-jp-corporate/jp-corporate.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-plugrail-jp-corporate/jp-corporate.json
- HTML version of this page: https://verifymcp.io/servers/dev-plugrail-jp-corporate/jp-corporate