Japan Procurement
NPM · @PIPEWORX/MCP-JAPAN-PROCUREMENT · 2 COMPONENTS
Japan Procurement MCP — Japanese government tender notices (bid announcements) from national…
Available components
Last scanned (2 hours ago)
Scores higher than 72% of npm servers
Category Search and Retrieval
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-japan-procurement). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1130 tokens (~282/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 Management23
- Stability observed for 7 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-japan-procurement@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-japan-procurement |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-japan-procurement/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3649444953 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:79eec3726bfe39a6dbbbb7bb6a86ab8cfb8fcaba2880a48c77726bbe2886f85cb9dd2964d5e1eb069975d1fbd64a25bb2c1a9a3a41fb76e4a58a9d8c6 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
japan_tender_reference ~69
Reference values accepted by the Japanese tender search tools: the three procurement categories, the notice/procedure types, and all 47 JIS X0401 prefecture codes with Japanese and romanised names. Call this when a filter value is rejected or when you need the code for a prefecture.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
japan_tenders_by_organization ~268
List Japanese government tender notices published by a named buyer — a ministry, agency, prefecture or city — matched on partial organisation name (e.g. "国土交通省", "防衛省", "横浜市"). Sourced from the 官公需情報ポータルサイト (Kankoju public procurement portal, Japan SME Agency). Optionally narrowed by category, keyword and announcement date range.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | One of goods | works | services (or 物品 | 工事 | 役務, or 1 | 2 | 3). |
| full_text | boolean | – | Return the full announcement text instead of a preview. Default false. |
| issued_from | string | – | Earliest announcement date (公告日), YYYY-MM-DD. |
| issued_to | string | – | Latest announcement date (公告日), YYYY-MM-DD. |
| limit | number | – | Max notices to return, 1-1000. Default 20. |
| organization_name | string | yes | Buyer organisation, partial match, in Japanese — e.g. "国土交通省" (MLIT), "経済産業省" (METI), "札幌市". |
| query | string | – | Optional keyword to narrow within the organisation. |
No output schema declared.
No examples provided.
japan_tenders_by_prefecture ~278
List Japanese government tender notices for one or more prefectures without needing a keyword — the way to browse what a given prefecture published recently. Sourced from the 官公需情報ポータルサイト (Kankoju public procurement portal, Japan SME Agency). Accepts a prefecture name ("Osaka", "大阪府") or JIS X0401 code ("27"), optionally narrowed by category, announcement date range and keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | One of goods | works | services (or 物品 | 工事 | 役務, or 1 | 2 | 3). |
| full_text | boolean | – | Return the full announcement text instead of a preview. Default false. |
| issued_from | string | – | Earliest announcement date (公告日), YYYY-MM-DD. |
| issued_to | string | – | Latest announcement date (公告日), YYYY-MM-DD. |
| limit | number | – | Max notices to return, 1-1000. Default 20. |
| prefecture | string | yes | Prefecture name ("Tokyo", "東京都") or JIS X0401 code ("13"). Comma-separate for several. Codes are zero-padded for you — a bare "1" returns nothing upstream. |
| query | string | – | Optional keyword to narrow within the prefecture. |
No output schema declared.
No examples provided.
japan_tenders_search ~458
Search Japanese government tender notices (bid announcements) by keyword across national ministries, all 47 prefectures and municipalities. Sourced from the 官公需情報ポータルサイト (Kankoju public procurement portal) run by the Japan SME Agency. Query accepts Japanese or ASCII text and the portal's operators: "A AND B", "A OR B", "A ANDNOT B", "NOT A", parentheses. Filter by category (goods/works/services), prefecture, procedure type and announcement date range. Returns buyer organisation, notice title, announcement date, bid/opening dates where published, the original notice URL and attachment links.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | One of goods | works | services (or 物品 | 工事 | 役務, or 1 | 2 | 3). |
| full_text | boolean | – | Return the full announcement text instead of a preview. The full text is often tens of thousands of characters; default false. |
| issued_from | string | – | Earliest announcement date (公告日), YYYY-MM-DD. |
| issued_to | string | – | Latest announcement date (公告日), YYYY-MM-DD. |
| limit | number | – | Max notices to return, 1-1000. Default 20. |
| organization_name | string | – | Restrict to a buyer organisation, partial match — e.g. "国土交通省", "横浜市". |
| prefecture | string | – | Prefecture to restrict to — name ("Tokyo", "東京都") or JIS X0401 code ("13"). Comma-separate for several ("Tokyo,Osaka"). |
| procedure_type | string | – | Notice type: 1 = 一般競争入札 (open competitive bidding), 2 = 簡易公募型競争入札, 3 = 簡易公募型指名競争入札. |
| project_name | string | – | Restrict by notice title, partial match. |
| query | string | yes | Keyword, Japanese or ASCII — e.g. "道路" (road), "システム" (system), "橋梁 AND 補修". Operators AND / OR / ANDNOT / NOT need surrounding spaces. |
No output schema declared.
No examples provided.
How do I install the Japan Procurement MCP server?
Japan Procurement runs locally as an npm package, launched with npx -y @pipeworx/mcp-japan-procurement. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-japan-procurement
claude mcp add pipeworx-io-japan-procurement -- npx -y @pipeworx/mcp-japan-procurement
What is the Japan Procurement MCP server?
Japan Procurement is an MCP server listed in the public MCP registry as io.github.pipeworx-io/japan-procurement. Japan Procurement MCP, Japanese government tender notices (bid announcements) from national… This page covers its npm package (@pipeworx/mcp-japan-procurement).
Is the Japan Procurement MCP server safe to use?
Japan Procurement scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Japan Procurement MCP server expose?
Japan Procurement exposes 4 tools: japan_tenders_search, japan_tenders_by_prefecture, japan_tenders_by_organization, japan_tender_reference. Their descriptions and schemas cost roughly 1,073 tokens of context every time the server is loaded.
Is the Japan Procurement MCP server still maintained?
Japan Procurement is still listed as active in the MCP registry. We last reached this channel on 5 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 Japan Procurement MCP server under?
Japan Procurement declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.