Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/sugukurukabe/koko-call-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/sugukurukabe/koko-call-mcp/jp-bids)<a href="https://agentmods.dev/mcp/sugukurukabe/koko-call-mcp/jp-bids"><img src="https://agentmods.dev/badge/mcp/sugukurukabe/koko-call-mcp/jp-bids/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/sugukurukabe/koko-call-mcp/jp-bids"><img src="https://agentmods.dev/badge/mcp/sugukurukabe/koko-call-mcp/jp-bids.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
jp-bids scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"jp-bids": {
"command": "npx",
"args": [
"-y",
"jp-bids-mcp"
],
"env": {}
}
}What else server.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 10 lines scan A b754882a4fc2
jp-bids is an MCP server published in the GitHub repository sugukurukabe/koko-call-mcp (0 stars, last pushed 12d ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
federal-compass
Your AI compass from private sector to federal career — MCP server for USAJobs API. Runs locally from the federal-compass-mcp npm package. Needs 2 environment variables to run.
federal-compass-mcp
AI compass from private sector to federal career — USAJobs search, salary, KSA. Runs locally from the federal-compass-mcp npm package. Needs 2 environment variables to run.
simap-mcp
MCP server for simap.ch - Swiss public procurement platform. Runs locally from the @digilac/simap-mcp npm package.
senado-br-mcp-cloudflare
MCP server for Brazilian Federal Senate open data (legislative, administrative, e-Cidadania). Runs locally from the senado-br-mcp npm package.
mcp-zakupki
A local connector for searching Russian government procurement records on zakupki.gov.ru, the official website for public tenders. It covers procedures governed by Russia's 44-FZ and 223-FZ laws and 615-PP rules.
jma-data-mcp
MCP server "jma-data-mcp" as configured in koizumikento/jma-data-mcp. Runs locally from the jma-data-mcp Python package.