Bango API(法人番号・インボイス)
NPM · BANGO-MCP · 2 COMPONENTS
Find Japanese companies by name; get corporate numbers, addresses and invoice (T-number) status.
Available components
Last scanned (16 hours ago)
Scores higher than 49% of npm servers
Category CRM and Sales
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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.
- 20 Nov 26 +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.
- 18 Nov 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.
- 17 Nov 26 +4
- Stability: unverified → 0.27 ▲ functional
- 9 Nov 26 68
First indexed and scored.
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 · Analysed npm/bango-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
bango_check_invoice インボイス登録番号が有効か確かめる ~248
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | この日付時点で有効だったかを判定する(YYYY-MM-DD、2024/10/1 なども可)。省略時は今日 |
| registration_numbers | array | yes | 確認したい登録番号の配列(1〜20件)。例: ["T1180301018771"] |
No output schema declared.
No examples provided.
bango_find_company 会社名から法人を探す ~330
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | yes | 会社名(一部でも可)。例: 「サンプル商事」「株式会社サンプル」 |
| exact | boolean | – | true にすると表記ゆれを吸収したうえでの完全一致だけを返す。既定は部分一致(false) |
| limit | integer | – | 返す候補の数(1〜20、既定5) |
| post_code | string | – | 郵便番号(7桁、ハイフン可)で絞り込む |
| prefecture | string | – | 都道府県で絞り込む。「大阪」「大阪府」「27」「osaka」のどれでも可 |
No output schema declared.
No examples provided.
bango_get_company 法人番号・T番号から会社情報を調べる ~232
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.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | 法人番号(13桁)またはインボイス登録番号(T+13桁) |
| response_format | string | – | concise(既定)は要点だけ。detailed はAPIの全項目(英語名、変更履歴など)も含める |
No output schema declared.
No examples provided.
bango_match_companies 会社名の一覧に法人番号をまとめて付ける(名寄せ) ~223
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.
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | – | 会社名の配列(1〜50件)。文字列か {name, prefecture} の形 |
| job_id | string | – | 前回の呼び出しで返った job_id。結果の取得だけを行う |
No output schema declared.
No examples provided.
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.
npm · bango-mcp
claude mcp add taku1211-bango-mcp -- npx -y bango-mcp
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.