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/neostorm112-boop/proxykey-mcpWrote 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/neostorm112-boop/proxykey-mcp/proxykey)<a href="https://agentmods.dev/mcp/neostorm112-boop/proxykey-mcp/proxykey"><img src="https://agentmods.dev/badge/mcp/neostorm112-boop/proxykey-mcp/proxykey/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/neostorm112-boop/proxykey-mcp/proxykey"><img src="https://agentmods.dev/badge/mcp/neostorm112-boop/proxykey-mcp/proxykey.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
proxykey 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
{
"proxykey": {
"url": "https://mcp.proxykey.org/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.
- 1mo ago First seen · 6 lines scan A 60724e8361ec
proxykey is an MCP server published in the GitHub repository neostorm112-boop/proxykey-mcp (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
unraid-mcp
MCP Server for Unraid API - provides tools to interact with an Unraid server's GraphQL API. Runs locally from the unraid-mcp Python package. Needs 3 environment variables to run.
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.
zendesk-local-http
MCP server "zendesk-local-http", hosted remotely at localhost, as configured in fruggr/zendesk-mcp-server.
guniweb-sap-mcp
SAP S/4HANA and ECC: OData V2/V4, IDoc and RFC/BAPI for n8n and other MCP clients. Runs locally from the guniweb-sap-mcp npm package. Needs 6 environment variables to run.
virtualsms
Real physical SIMs for AI agents: SMS verification and rentals. 145+ countries, 2500+ services. Runs locally from the virtualsms-mcp npm package. Needs 1 environment variable to run.
bitbucket-mcp
MCP Server for Bitbucket API - Container optimized with configurable tools, structured output and slim responses. Runs locally from the bitbucket-mcp-py Python package.