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.
npx agentmods add mcp/aolingge/agent-reliability-kit/mcp-registry-browsergit clone --depth 1 https://github.com/aolingge/agent-reliability-kitWrote 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/aolingge/agent-reliability-kit/mcp-registry-browser)<a href="https://agentmods.dev/mcp/aolingge/agent-reliability-kit/mcp-registry-browser"><img src="https://agentmods.dev/badge/mcp/aolingge/agent-reliability-kit/mcp-registry-browser.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
browser 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 4d 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
{
"browser": {
"url": "https://unapproved.example/mcp"
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 4d ago First seen · 5 lines scan A 1a20c36fc117
browser is an MCP server published in the GitHub repository aolingge/agent-reliability-kit (2 stars, last pushed 1mo 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
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
exa
Exa's hosted MCP server: neural web search and page content for the agent. Remote server at mcp.exa.ai. Needs 1 environment variable to run.
trusty-squire
Trusty Squire signs up / in to websites for you so you don’t have to. Runs locally from the @trusty-squire/mcp npm package.
playwright
Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.
apify
Apify MCP Server. Runs locally from the @apify/actors-mcp-server npm package. Needs 2 environment variables to run.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.