JP Bids

io.github.sugukurukabePublished by GitHub account sugukurukabev0.9.0Updated Oct 24, 2026

Read-only MCP server for searching Japan government procurement bid information from the KKJ portal.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Read-only MCP server that lets an assistant search Japanese government procurement (KKJ) bid notices.

What you can do
This server lets an assistant search Japanese government procurement bid information from the KKJ portal. It is read-only and focuses on querying tender notices rather than submitting bids or changing data.
When to use it
Use it when an assistant needs to look up Japanese government procurement notices, find bidding opportunities, or research public procurement data. It is read-only and not intended for submitting bids or managing tender workflows.
Requirements
A remote endpoint connection, or the npm package jp-bids-mcp run locally over stdio; OAuth authentication is required, and network access is needed.
Before you install
Requires OAuth authorization, so check the scope and which account data it can access before installing. The service is read-only and does not write or change data.

Installation

In SourceWeft

  1. Open JP Bids in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.sugukurukabe%2Fjp-bids/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "jp-bids": {
      "type": "http",
      "url": "https://mcp.bid-jp.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.9.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.