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/kamy-development/kamy-plugin/kamygit clone --depth 1 https://github.com/Kamy-Development/kamy-pluginGrade A, and why
kamy 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 yesterday.
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
{
"kamy": {
"type": "http",
"url": "https://mcp.kamy.dev",
"description": "Kamy PDF generation MCP server. Exposes tools for rendering PDFs, listing templates, and inspecting recent renders. Authenticate with a Kamy API key from https://kamy.dev/dashboard/keys passed as `Authorization: Bearer <key>`.",
"headers": {
"Authorization": "Bearer ${KAMY_API_KEY}"
}
}
}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.
- yesterday First seen · 10 lines scan A 4dcdc3ba344c
kamy is an MCP server published in the GitHub repository Kamy-Development/kamy-plugin (0 stars, last pushed 3mo 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
papi
MCP server "papi", hosted remotely at mcp.getpapi.ai, as configured in getpapi/papi.
toon-memory
Offline persistent memory for AI coding agents — 35 tools, 80% fewer calls, no LLM. Runs locally from the toon-memory npm package. Needs 6 environment variables to run.
savee
MCP server "savee", hosted remotely at mcp.savee.com, as configured in saveeit/savee-mcp-server.
mcp
Official GetXAPI MCP server — use the Twitter/X API (search, users, tweets, posting, DMs, articles) inside Claude, Cursor, and any MCP client. Runs locally from the @getxapi/mcp npm package.
samotpravil-api-mcp
MCP server for Samotpravil SMTP API — documentation search and API proxy. Interim npm: samotpravil-mcp; future: @samotpravil/mcp after org migration. Runs locally from the samotpravil-mcp npm package. Needs 11 environment variables to run.
spotify-mcp
Conversational Spotify control from AI clients: play, queue, devices, playlists, and library. Runs locally from the @xavifabregat/spotify-mcp npm package.