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/Kokai-Data/japan-business-dataWrote 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/kokai-data/japan-business-data/kokai-data-kokai)<a href="https://agentmods.dev/mcp/kokai-data/japan-business-data/kokai-data-kokai"><img src="https://agentmods.dev/badge/mcp/kokai-data/japan-business-data/kokai-data-kokai/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/kokai-data/japan-business-data/kokai-data-kokai"><img src="https://agentmods.dev/badge/mcp/kokai-data/japan-business-data/kokai-data-kokai.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
kokai 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 11d 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
{
"kokai": {
"type": "http",
"url": "https://mcp.kokai.ai/functions/v1/mcp-server",
"headers": {
"x-kokai-beta-client-id": "${KOKAI_MCP_CLIENT_ID:-kokai-plugin-shared-default}"
}
}
}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.
- 11d ago First seen · 9 lines scan A 97f3f2960439
kokai is an MCP server published in the GitHub repository Kokai-Data/japan-business-data (2 stars, last pushed 2mo 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
redash-mcp
Connect Redash to Claude -- query data, manage dashboards, and run SQL with natural language. Runs locally from the redash-mcp npm package. Needs 5 environment variables to run.
odoo-pulse
AI business analyst for Odoo ERP (18+) — one-call reports with verdicts, over MCP. Runs locally from the odoo-pulse Python package. Needs 5 environment variables to run.
mcp-trustlayer
MCP server "mcp-trustlayer" as configured in neelbarm/mcp-trustlayer. Runs locally from the mcp-trustlayer Python package.
memocall
Recall past Claude Code conversations from any project as clean, compact Markdown. Runs locally from the memocall npm package.
mcp-bash-server
MCP server "mcp-bash-server" as configured in uditk2/mcp-bash-server. Runs locally from the mcp-bash-server Python package.
tracer
MCP server "tracer" as configured in aiquilibria/contAIned. Runs contained.tracer_mcp with python3.