# Japan Procurement (npm · @pipeworx/mcp-japan-procurement)

Japan Procurement MCP — Japanese government tender notices (bid announcements) from national…

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-japan-procurement/japan-procurement-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-japan-procurement/japan-procurement-mcp)
- npm · `@pipeworx/mcp-japan-procurement`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-japan-procurement/pipeworx-mcp-japan-procurement.md), [page](https://verifymcp.io/servers/pipeworx-io-japan-procurement/pipeworx-mcp-japan-procurement)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-japan-procurement`
- Version: `0.2.1`
- 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-05.

- **Supply Chain Security**: 100/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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-japan-procurement).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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 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.

### Claude

```bash
claude mcp add pipeworx-io-japan-procurement -- npx -y @pipeworx/mcp-japan-procurement
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-japan-procurement": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-japan-procurement"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-japan-procurement": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-japan-procurement"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-japan-procurement -- npx -y @pipeworx/mcp-japan-procurement
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-japan-procurement": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-japan-procurement"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-japan-procurement --command npx --arg -y --arg @pipeworx/mcp-japan-procurement
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-japan-procurement:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-japan-procurement"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-japan-procurement": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-japan-procurement"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-japan-procurement -t stdio -c npx -a -y @pipeworx/mcp-japan-procurement
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-japan-procurement": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-japan-procurement"
      ]
    }
  }
}
```

## 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-05 (score 82, +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.

### 2026-11-03 (score 81, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 65, −13)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.13
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-31 (score 78, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (4)

### `japan_tenders_search` (~458 tokens)

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.

Input parameters:

- `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, required): Keyword, Japanese or ASCII — e.g. "道路" (road), "システム" (system), "橋梁 AND 補修". Operators AND / OR / ANDNOT / NOT need surrounding spaces.

### `japan_tenders_by_prefecture` (~278 tokens)

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.

Input parameters:

- `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, required): 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.

### `japan_tenders_by_organization` (~268 tokens)

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.

Input parameters:

- `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, required): Buyer organisation, partial match, in Japanese — e.g. "国土交通省" (MLIT), "経済産業省" (METI), "札幌市".
- `query` (string): Optional keyword to narrow within the organisation.

### `japan_tender_reference` (~69 tokens)

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.

## Diagnostics

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

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 65
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

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

### What did VerifyMCP test on the Japan Procurement MCP server?

VerifyMCP ran 16 checks on Japan Procurement, 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/@pipeworx/mcp-japan-procurement
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-japan-procurement
- Repository: https://github.com/pipeworx-io/mcp-japan-procurement
- Website: https://pipeworx.io/packs/japan-procurement
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-japan-procurement/pipeworx-mcp-japan-procurement.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-japan-procurement/pipeworx-mcp-japan-procurement/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-japan-procurement/pipeworx-mcp-japan-procurement.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-japan-procurement/pipeworx-mcp-japan-procurement