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/jadchene/mcp-gatewayWrote 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/jadchene/mcp-gateway/mcp-gateway-service)<a href="https://agentmods.dev/mcp/jadchene/mcp-gateway/mcp-gateway-service"><img src="https://agentmods.dev/badge/mcp/jadchene/mcp-gateway/mcp-gateway-service/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/jadchene/mcp-gateway/mcp-gateway-service"><img src="https://agentmods.dev/badge/mcp/jadchene/mcp-gateway/mcp-gateway-service.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-gateway-service 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 11d 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
{ "mcp-gateway-service": { "command": "npx", "args": [ "-y", "@jadchene/mcp-gateway-service" ] } }
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.
- 11d ago First seen · 9 lines scan A 9fc14a6929cc
mcp-gateway-service is an MCP server published in the GitHub repository jadchene/mcp-gateway (0 stars, last pushed 26d 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
perfume-picks
Search the Perfume Picks fragrance database: 13,000+ scents with notes, dupes, and wear data. Runs locally from the perfume-picks-mcp npm package.
pour-picks
Search the Pour Picks bourbon & whiskey database: 4,700+ bottles with tasting profiles and prices. Runs locally from the pour-picks-mcp npm package.
ollama-web-search
MCP stdio server exposing Ollama's hosted web search and web fetch APIs as tools for any MCP client. Runs locally from the ollama-web-search Python package.
shotplan
MCP server "shotplan" as configured in lrvaka/shotplan. Runs locally from the shotplan-mcp Python package. Needs 3 environment variables to run.
registry
The evidence layer for MCP: live operational grades plus Trust Receipts for every registry server. Remote server at mcpqueen.com.
mcp-test
MCP server "mcp-test", hosted remotely at localhost, as configured in plexara/mcp-test.