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/wheattoast11/openrouter-deep-research-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/wheattoast11/openrouter-deep-research-mcp/openrouter-agents)<a href="https://agentmods.dev/mcp/wheattoast11/openrouter-deep-research-mcp/openrouter-agents"><img src="https://agentmods.dev/badge/mcp/wheattoast11/openrouter-deep-research-mcp/openrouter-agents/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/wheattoast11/openrouter-deep-research-mcp/openrouter-agents"><img src="https://agentmods.dev/badge/mcp/wheattoast11/openrouter-deep-research-mcp/openrouter-agents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
openrouter-agents 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
{
"openrouter-agents": {
"command": "node",
"args": [
"/var/home/zero/terminals-tech/src/server/mcpServer.js",
"--stdio"
],
"env": {
"OPENROUTER_API_KEY": "${OPENROUTER_API_KEY}",
"INDEXER_ENABLED": "true",
"MCP_ENABLE_TASKS": "true",
"MCP_SAMPLING_TOOLS": "true",
"MCP_ELICITATION_URL": "true"
}
}
}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 · 16 lines scan A 4e95785a1314
openrouter-agents is an MCP server published in the GitHub repository wheattoast11/openrouter-deep-research-mcp (55 stars, last pushed 10d 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-30.
Other mcp servers, from other repositories
stickyinc
MCP server "stickyinc" as configured in Astralchemist/stickyinc. Runs locally from the stickyinc npm package.
unified
MCP server "unified" as configured in getfounded/mcp-tool-kit. Runs in Docker.
chromium-mcp
MCP server "chromium-mcp" as configured in gzigurella/chromium-mcp. Runs locally from the chromium-mcp Python package.
url-content-mcp
MCP server "url-content-mcp" as configured in artryazanov/url-content-mcp. Runs locally from the url-content-mcp Python package.
context7
Gives the agent up-to-date documentation and code examples for libraries and frameworks, fetched on demand so answers are not stuck at the model's training cutoff. Runs locally from the @upstash/context7-mcp npm package. Needs 1 environment variable to run.
hackmd-mcp
A Model Context Protocol server for integrating HackMD's note-taking platform with AI assistants. Runs locally from the hackmd-mcp npm package. Needs 2 environment variables to run.