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/techwell-inc-jp/shirabe-calendar-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/techwell-inc-jp/shirabe-calendar-api/hub)<a href="https://agentmods.dev/mcp/techwell-inc-jp/shirabe-calendar-api/hub"><img src="https://agentmods.dev/badge/mcp/techwell-inc-jp/shirabe-calendar-api/hub/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/techwell-inc-jp/shirabe-calendar-api/hub"><img src="https://agentmods.dev/badge/mcp/techwell-inc-jp/shirabe-calendar-api/hub.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
hub 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 8d 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
{
"hub": {
"url": "https://shirabe.dev/mcp",
"type": "streamable-http"
}
}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.
- 8d ago First seen · 6 lines scan A 53740c7507b8
hub is an MCP server published in the GitHub repository techwell-inc-jp/shirabe-calendar-api (0 stars, last pushed 1mo ago), licensed MIT. 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
tokyo-opendata-mcp
MCP server "tokyo-opendata-mcp" as configured in bitpackman/tokyo-opendata-mcp. Runs locally from the tokyo-opendata-mcp npm package.
food-db
Resolve Japanese food names to nutrition facts. All 2,538 foods from Japan's official tables. Remote server at toriigate.dev.
japan-data-api
Deep, obscure Japanese station, accessibility & hazard data for AI agents. English-first. Remote server at api.gachi-tokusuru.com.
tako-mcp
Search, answer, and fetch Tako's knowledge base of 100K+ data charts, plus deep research agents. Remote server at mcp.tako.com.
mcp-server
WasmAgent MCP server — WASM-sandboxed code execution with capability manifests and Tasks API. Runs locally from the @wasmagent/mcp-server npm package.
mcp-gsc
Google Search Console MCP for analytics, indexing, sitemaps, and SEO diagnostics. Runs locally from the @digestseo/mcp-gsc npm package.