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/churnkey/sdkWrote 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/churnkey/sdk/mcp-churnkey)<a href="https://agentmods.dev/mcp/churnkey/sdk/mcp-churnkey"><img src="https://agentmods.dev/badge/mcp/churnkey/sdk/mcp-churnkey/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/churnkey/sdk/mcp-churnkey"><img src="https://agentmods.dev/badge/mcp/churnkey/sdk/mcp-churnkey.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
churnkey 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 2mo 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
{
"churnkey": {
"url": "https://mcp.churnkey.co/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.
- 2mo ago First seen · 6 lines scan A 845885dbabf3
churnkey is an MCP server published in the GitHub repository churnkey/sdk (24 stars, last pushed yesterday), 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-30.
Other mcp servers, from other repositories
next-devtools
Next.js development tools MCP server with stdio transport. Runs locally from the next-devtools-mcp npm package.
usefillo
Fillo MCP server — provision, scaffold, publish, and query forms from your coding agent. Runs locally from the @usefillo/mcp npm package.
fillo
MCP server "fillo", hosted remotely at fillo.so, as configured in jacobfunch/usefillo.
harukibox
Run a Japan proxy-buying business from your AI: inventory, orders, buyers, shipping fee split. Runs locally from the @harukibox/mcp npm package. Needs 2 environment variables to run.
swell
Model Context Protocol server for Swell e-commerce platform integration with AI assistants. Runs locally from the swell-mcp npm package. Needs 2 environment variables to run.
hotelbooking
A local connection for searching or booking hotels through the RollingGo hotel-booking service. It requires an API key, which is a credential that lets software access the service.