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.
npx agentmods add mcp/eng213035/gachi-data-api/japan-data-apigit clone --depth 1 https://github.com/eng213035/gachi-data-apiWrote 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/eng213035/gachi-data-api/japan-data-api)<a href="https://agentmods.dev/mcp/eng213035/gachi-data-api/japan-data-api"><img src="https://agentmods.dev/badge/mcp/eng213035/gachi-data-api/japan-data-api.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
japan-data-api 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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 6 lines scan A 99c19acac906
japan-data-api is an MCP server published in the GitHub repository eng213035/gachi-data-api (1 stars, last pushed 3d ago), with no licence file. 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
japan-seasons
Live Japan seasonal travel MCP: sakura, autumn leaves, flowers, festivals, fruit farms, weather. Runs locally from the japan-seasons-mcp npm package. Needs 4 environment variables to run.
food-db
Resolve Japanese food names to nutrition facts. All 2,538 foods from Japan's official tables. Remote server at toriigate.dev.
mcp-ts-core
Agent-native TypeScript framework for building MCP servers with declarative definitions. Runs locally from the @cyanheads/mcp-ts-core npm package. Needs 1 environment variable to run.
mcp-web-validator
W3C HTML/CSS Validator and Technical SEO Audit MCP Server for AI coding assistants. Runs locally from the mcp-web-validator 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.
agent-audit
Turn Lighthouse audits into coding-agent fix packs for Claude Code, Cursor, and Copilot. Runs locally from the @fullstackdegen/agent-audit npm package.