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/eidos-agi/research.mdWrote 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/eidos-agi/research.md/research-md)<a href="https://agentmods.dev/mcp/eidos-agi/research.md/research-md"><img src="https://agentmods.dev/badge/mcp/eidos-agi/research.md/research-md/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/eidos-agi/research.md/research-md"><img src="https://agentmods.dev/badge/mcp/eidos-agi/research.md/research-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
research-md 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
{ "research-md": { "command": "uvx", "args": [ "research-md" ] } }
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 · 8 lines scan A 99842670a25e
research-md is an MCP server published in the GitHub repository eidos-agi/research.md (0 stars, last pushed 2mo 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
solana-dev
MCP server "solana-dev", hosted remotely at mcp.solana.com, as configured in GeckoVision/gecko-surf.
zerodust
Recover stranded native gas: empty a chain's balance to exactly zero on 25 EVM chains. Runs locally from the @zerodust/mcp-server npm package. Needs 10 environment variables to run.
local-gpu-imagegen
MCP server "local-gpu-imagegen" as configured in ChevalGrand520/local-gpu-imagegen. Runs scripts/mcp_server.py with python.
domain-search-king-mcp
Domain search MCP: .com names verified available live via Verisign RDAP - not AI guess lists. Remote server at domainsearchking.com.
mcp-server
Pay-per-call AI + web + on-chain tools over x402 (USDC on Base): LLM, SEO, extract, token safety. Runs locally from the @true402.dev/mcp-server npm package. Needs 3 environment variables to run.
agentstack-mcp
Deterministic reasoning stack for AI agents: simulate, decide & compute, plus cross-domain tools. Runs locally from the agentstack-mcp npm package.