Koskamo

Pipeworx Japan Procurement MCP

Document v1 · published by Koskamo · updated 2026-10-05

Original source

This MCP server provides access to Japanese government tender notices and bid announcements from national ministries, all 47 prefectures, and municipalities. It sources data from the Kankoju public procurement portal run by the Japan SME Agency, offering tools to search by keyword, prefecture, or organization.

  • Operator: Pipeworx
  • Endpoint: https://gateway.pipeworx.io/japan-procurement/mcp
  • Transport: streamable-http
  • Sign-in: No sign-in
  • Category: Data and analytics
  • Use cases: Search Japanese government tender notices by keyword; List tender notices for specific prefectures; Find tenders published by specific government organizations; Retrieve reference values for procurement categories and codes
  • Tools: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, search_within, deep_research, discover_tools, resolve_entity, compare_entities, subscribe, unsubscribe, list_subscriptions, recent_alerts, entity_profile, recent_changes, validate_claim, company_facts, scan_dependency, bet_research, polymarket_arbitrage, polymarket_edges, polymarket_kalshi_spread, polymarket_fill_risk, polymarket_edge_tracker, kalshi_weather_edge, resolution_audit, resolution_diff, release_calendar_markets, pipeworx_trending, suggest_questions, generate_llms_txt, ai_visibility_check, scan_competitor_ai_presence, pipeworx_feedback, remember, recall, forget, japan_tenders_search, japan_tenders_by_prefecture, japan_tenders_by_organization, japan_tender_reference
  • Documentation: https://pipeworx.io/packs/japan-procurement
  • Directory listing: https://koskamo.com/explore/pipeworx-japan-procurement-mcp
  • Also known as: Pipeworx Japan Procurement MCP MCP; pipeworx-japan-procurement-mcp

Source and provenance

Original source
pipeworx.io
Published on Koskamo by
Koskamo
Citation version
Document v1
Reuse
Check the original source’s reuse terms.

This record mirrors the MCP server directory listing and updates when the listing changes. To correct it, suggest an edit on the listing.

Version history

  1. Synced from the directory

    Version 2

  2. Synced from the directory

    Version 1