# Bango API（法人番号・インボイス） (npm · bango-mcp)

Find Japanese companies by name; get corporate numbers, addresses and invoice (T-number) status.

- Trust score: 74/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.bango-api.jp`: 36/100, [markdown](https://verifymcp.io/servers/taku1211-bango-mcp/mcp.md), [page](https://verifymcp.io/servers/taku1211-bango-mcp/mcp)
- npm · `bango-mcp`: 74/100 (this document), [markdown](https://verifymcp.io/servers/taku1211-bango-mcp/bango-mcp.md), [page](https://verifymcp.io/servers/taku1211-bango-mcp/bango-mcp)

## Channel facts

- Registry: `npm`
- Package: `bango-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 12 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1236 tokens (~309/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Bango API（法人番号・インボイス） MCP server?

Bango API（法人番号・インボイス） runs locally as an npm package, launched with npx -y bango-mcp. 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 taku1211-bango-mcp -- npx -y bango-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "taku1211-bango-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "bango-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "taku1211-bango-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "bango-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add taku1211-bango-mcp -- npx -y bango-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "taku1211-bango-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "bango-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add taku1211-bango-mcp --command npx --arg -y --arg bango-mcp
```

### Hermes

```yaml
mcp_servers:
  taku1211-bango-mcp:
    command: "npx"
    args: ["-y", "bango-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "taku1211-bango-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "bango-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add taku1211-bango-mcp -t stdio -c npx -a -y bango-mcp
```

### Other

```json
{
  "mcpServers": {
    "taku1211-bango-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "bango-mcp"
      ]
    }
  }
}
```

## 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-11-20 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 73, +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.

### 2026-11-17 (score 72, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-11-09 (score 68)

First indexed and scored.

## MCP tools (4)

### `bango_find_company` (~330 tokens)

会社名から法人を探す

Find Japanese companies (法人) by name and return candidate corporate numbers (法人番号). Use this when the user gives a company name instead of a number, e.g. 「トヨタ自動車」「㈱サンプル 大阪」「sample shoji」. Name variants are absorbed automatically (株式会社/㈱/(株), full-width/half-width, spaces), so pass the name as the user wrote it; do not guess a 13-digit number. Narrow with prefecture when the user mentions a place. Results are ranked by score (0-1). If several candidates look plausible, ask the user which one they mean (show name and prefecture) instead of picking one. Then call bango_get_company with the chosen corporate_number for address and invoice status. Each call uses 1 API request from the user's Bango API quota.

Input parameters:

- `company_name` (string, required): 会社名（一部でも可）。例: 「サンプル商事」「株式会社サンプル」
- `exact` (boolean): true にすると表記ゆれを吸収したうえでの完全一致だけを返す。既定は部分一致（false）
- `limit` (integer): 返す候補の数（1〜20、既定5）
- `post_code` (string): 郵便番号（7桁、ハイフン可）で絞り込む
- `prefecture` (string): 都道府県で絞り込む。「大阪」「大阪府」「27」「osaka」のどれでも可

### `bango_get_company` (~232 tokens)

法人番号・T番号から会社情報を調べる

Look up one Japanese company or invoice issuer by its corporate number (法人番号, 13 digits) or invoice registration number (登録番号, 'T' + 13 digits). Hyphens, spaces and full-width digits are accepted, e.g. 「T1-1803-0101-8771」. Returns official name, kana, address, whether the company is still active (閉鎖の有無), and its invoice registration status (有効/失効/登録取消/未登録). T-numbers of sole proprietors (個人事業主) also work, but personal address is returned only if the person chose to publish it. If you only have a company name, call bango_find_company first. Uses 1 API request.

Input parameters:

- `number` (string, required): 法人番号（13桁）またはインボイス登録番号（T+13桁）
- `response_format` (string): concise（既定）は要点だけ。detailed はAPIの全項目（英語名、変更履歴など）も含める

### `bango_check_invoice` (~248 tokens)

インボイス登録番号が有効か確かめる

Check whether invoice registration numbers (適格請求書発行事業者の登録番号, T + 13 digits) are valid, for one or many numbers at once (up to 20). Typical use: verifying the T-number printed on an invoice or receipt before claiming input tax credit (仕入税額控除). Without `date`, checks validity as of today (JST) and also returns the registered name so the user can compare it with the invoice. With `date` (e.g. the invoice issue date), checks validity on that date; the name is not returned in that mode. A number with only 13 digits is treated as a T-number. Invalid or unknown numbers are reported per item and do not fail the whole call. Uses 1 API request per number.

Input parameters:

- `date` (string): この日付時点で有効だったかを判定する（YYYY-MM-DD、2024/10/1 なども可）。省略時は今日
- `registration_numbers` (array, required): 確認したい登録番号の配列（1〜20件）。例: ["T1180301018771"]

### `bango_match_companies` (~223 tokens)

会社名の一覧に法人番号をまとめて付ける（名寄せ）

Match a list of company names (e.g. a customer list, sales list, or vendor master from a spreadsheet) to corporate numbers in one go (名寄せ). Each row gets a confidence: 'confident' (safe to use), 'review' (several close candidates; show them to the user), or 'unmatched'. Pass up to 50 names per call; adding a prefecture per row improves accuracy. The job usually finishes within seconds. If it is still running when this tool returns, call it again with the returned job_id (and no companies) to fetch the result; do not resubmit the list. Uses batch-row quota (Free plan: 50 rows per month). For a single company, bango_find_company is cheaper.

Input parameters:

- `companies` (array): 会社名の配列（1〜50件）。文字列か {name, prefecture} の形
- `job_id` (string): 前回の呼び出しで返った job_id。結果の取得だけを行う

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/taku1211-bango-mcp/bango-mcp#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 74
- 2026-11-19: 73
- 2026-11-18: 73
- 2026-11-17: 72
- 2026-11-16: 68
- 2026-11-15: 68
- 2026-11-14: 68
- 2026-11-13: 68
- 2026-11-12: 68
- 2026-11-11: 68
- 2026-11-10: 68
- 2026-11-09: 68

## Common questions

### What is the Bango API（法人番号・インボイス） MCP server?

Bango API（法人番号・インボイス） is an MCP server listed in the public MCP registry as io.github.taku1211/bango-mcp. Find Japanese companies by name; get corporate numbers, addresses and invoice (T-number) status. This page covers its npm package (bango-mcp).

### Is the Bango API（法人番号・インボイス） MCP server safe to use?

Bango API（法人番号・インボイス） scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 Bango API（法人番号・インボイス） MCP server expose?

Bango API（法人番号・インボイス） exposes 4 tools: bango_find_company, bango_get_company, bango_check_invoice, bango_match_companies. Their descriptions and schemas cost roughly 1,033 tokens of context every time the server is loaded.

### Is the Bango API（法人番号・インボイス） MCP server still maintained?

Bango API（法人番号・インボイス） 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 licence is the Bango API（法人番号・インボイス） MCP server under?

Bango API（法人番号・インボイス） declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Bango API（法人番号・インボイス） MCP server?

VerifyMCP ran 16 checks on Bango API（法人番号・インボイス）, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/bango-mcp
- Socket report: https://socket.dev/npm/package/bango-mcp
- Repository: https://github.com/taku1211/bango-mcp
- Website: https://bango-api.jp/
- Changelog RSS feed: https://verifymcp.io/servers/taku1211-bango-mcp/bango-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/taku1211-bango-mcp/bango-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/taku1211-bango-mcp/bango-mcp.json
- HTML version of this page: https://verifymcp.io/servers/taku1211-bango-mcp/bango-mcp
