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/gmitch215/MyMCPWrote 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/gmitch215/mymcp/petstore)<a href="https://agentmods.dev/mcp/gmitch215/mymcp/petstore"><img src="https://agentmods.dev/badge/mcp/gmitch215/mymcp/petstore/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/gmitch215/mymcp/petstore"><img src="https://agentmods.dev/badge/mcp/gmitch215/mymcp/petstore.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
petstore 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 1mo 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
{
"petstore": {
"type": "http",
"url": "https://mymcp.gmitch215.xyz/petstore/mcp"
}
}What else .mcp.json configures
This page is one entry in a file that holds 4. 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.
- 1mo ago First seen · 6 lines scan A 6286a8cded27
petstore is an MCP server published in the GitHub repository gmitch215/MyMCP (7 stars, last pushed 3d ago), licensed MPL-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-09-10.
Other mcp servers, from other repositories
stitchapi-docs
StitchAPI documentation search, running locally over MCP stdio. Bundled docs, no network calls per query — the offline/air-gapped counterpart to the hosted stitchapi.dev/api/mcp server. Runs locally from the @stitchapi/docs-mcp npm package.
boxpdf
Resource-only MCP server with docs and templates for the boxpdf TypeScript PDF layout library. Runs locally from the boxpdf npm package.
callspec
Stop duct-taping your API stack. One TypeScript route → HTTP API server, MCP, SDK, docs, and OpenAPI. Runs locally from the callspec npm package.
mcp
Read any web page as clean Markdown for AI agents: fetch, search, metadata, links. SSRF-safe. Remote server at mcp.vanshul.com.
savepinner
Parse, validate, classify, and normalize Pinterest URLs locally without network requests. Runs locally from the savepinner-mcp npm package.
kimai-mcp-server
Kimai MCP server for Claude, Cursor, and AI agents: 16 tools covering the entire Kimai API. 13 curated time-tracking tools plus a 91-endpoint catalog, with per-call authorization, pre-write backups, cascade snapshots, and an environment gate on deletes. Runs locally from the @nightsquawktech/kimai-mcp-server npm…