@pipeworx/japan-procurement

Connect: https://gateway.pipeworx.io/japan-procurement/mcp · Install: one-click buttons

Tools: 4

Japanese government tender notices — bid announcements from national ministries, all 47 prefectures and municipalities, sourced from the 官公需情報ポータルサイト (Kankōju public procurement portal) run by the Japan Small and Medium Enterprise Agency.

Tools

• japan_tenders_search(query, …) — keyword search across every publishing body. Accepts Japanese or ASCII and the portal’s operators (AND / OR / ANDNOT / NOT, parentheses). Filters: category, prefecture, procedure type, organisation, notice title, announcement-date range.
• japan_tenders_by_prefecture(prefecture, …) — browse a prefecture’s notices with no keyword. Takes "Tokyo", "東京都" or "13", comma-separated for several.
• japan_tenders_by_organization(organization_name, …) — everything a named buyer published ("国土交通省", "横浜市"), partial match.
• japan_tender_reference() — the accepted categories, procedure types and all 47 JIS X0401 prefecture codes. Call it when a filter value is rejected.

Every notice carries the buyer, title, announcement date, the original notice URL, attachment links, and — where the publisher supplied them — the bid submission date, opening date, delivery deadline, performance location and required bidder certification.

Auth

Keyless.

Data sources

• https://www.kkj.go.jp/api/ — the portal’s documented search API, XML. Spec: https://www.kkj.go.jp/doc/ja/api_guide.pdf (V1.1, 2016-05-27).

Things the next person would otherwise rediscover the hard way:

• LG_Code must be zero-padded to two digits. LG_Code=1 returns SearchHits=0 — a clean 200 that reads as “Hokkaido publishes no tenders”. LG_Code=01 returns ~50k. The pack pads for you; don’t undo that.
• Category must be the numeric code (1 物品 / 2 工事 / 3 役務). Passing the Japanese label returns internal error: query error: syntax error. Same for Procedure_Type (1–3). The pack maps names and labels to codes and rejects anything unmappable with the valid set named, rather than forwarding it.
• No offset or page parameter exists. Count caps at 1,000 per call (values above that are silently treated as 1,000). To walk a larger result set, narrow with CFT_Issue_Date — the pack surfaces this as paging in the response whenever total_hits exceeds what it returned.
• At least one of Query / Project_Name / Organization_Name / LG_Code is required; with none the API answers <Error>no searchword</Error>. That is why the browse tools require a prefecture or an organisation.
• ProjectDescription is the full extracted notice text, routinely tens of thousands of characters (it is the OCR/extract of the linked PDF, and can include the whole unit-price schedule). The pack returns a 600-character preview with description_truncated, and up to 20,000 characters under full_text: true.
• Optional fields are omitted, not emptied, when the publisher did not supply them — TenderSubmissionDeadline, OpeningTendersEvent, Location, Certification and ItemCode are frequently absent, especially on municipal notices.

Tools

• japan_tenders_search — Search Japanese government tender notices (bid announcements) by keyword across national ministries, all 47 prefectures and municipalities. Sourced from the 官公需情報ポータルサイト (Kankoju public procurement po
• japan_tenders_by_prefecture — 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 pub
• japan_tenders_by_organization — 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 官公需情報ポ
• japan_tender_reference — 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. Ca