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/mp-juns/universal-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/mp-juns/universal-research-mcp/universal-research-memory-universal_research)<a href="https://agentmods.dev/mcp/mp-juns/universal-research-mcp/universal-research-memory-universal_research"><img src="https://agentmods.dev/badge/mcp/mp-juns/universal-research-mcp/universal-research-memory-universal_research/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/mp-juns/universal-research-mcp/universal-research-memory-universal_research"><img src="https://agentmods.dev/badge/mcp/mp-juns/universal-research-mcp/universal-research-memory-universal_research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
universal_research 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 10d 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
{
"universal_research": {
"type": "stdio",
"command": "universal-research",
"args": [
"serve",
"--no-auto-index"
]
}
}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.
- 10d ago First seen · 10 lines scan A a6aba43adc91
universal_research is an MCP server published in the GitHub repository mp-juns/universal-research-mcp (0 stars, last pushed 12d 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
warrant
Verify what an AI agent decided — signed, hash-addressed decision records with reasons you can re-run on your own machine. Runs locally from the warrant-verify Python package. Needs 3 environment variables to run.
notarize
Canonical trace format and verifier for agent execution attestation. Runs locally from the notarize-ai Python package.
krait-solodit
MCP server "krait-solodit" as configured in ZealynxSecurity/krait. Runs mcp-servers/solodit/build/index.js with node.
pseolint
Penalty-risk audit for programmatic SEO sites: verdict, risk score, and a fix manifest. Runs locally from the @pseolint/mcp npm package. Needs 2 environment variables to run.
matrixscroll
MCP server for signed machine-action records, offline tool-surface checks, and SSX360 USB signer support. Runs locally from the matrixscroll Python package.
agent-runtime-proof
MCP server "agent-runtime-proof" as configured in fantasyce/agent-runtime-proof. Launched with agent-runtime-proof mcp.