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/zlatanpham/ireader-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/zlatanpham/ireader-mcp/ireader)<a href="https://agentmods.dev/mcp/zlatanpham/ireader-mcp/ireader"><img src="https://agentmods.dev/badge/mcp/zlatanpham/ireader-mcp/ireader/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/zlatanpham/ireader-mcp/ireader"><img src="https://agentmods.dev/badge/mcp/zlatanpham/ireader-mcp/ireader.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ireader 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 9d 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
{ "ireader": { "command": "npx", "args": [ "-y", "@x-mcp/ireader" ] } }
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.
- 9d ago First seen · 9 lines scan A 19f78099472f
ireader is an MCP server published in the GitHub repository zlatanpham/ireader-mcp (1 stars, last pushed 1y 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-mcp
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.
mcp-server-browser
MCP server for browser use access. Runs locally from the @agent-infra/mcp-server-browser npm package. Needs 1 environment variable to run.
stdio-full
MCP server "stdio-full" as configured in apify/apify-mcp-server. Runs dist/stdio.js with node. Needs 2 environment variables to run.
apify-mcp-server
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡. Remote server at mcp.apify.com.
reddit-mcp-buddy
Reddit browser for AI assistants. Browse posts, search content, analyze users. No API keys needed. Runs locally from the reddit-mcp-buddy npm package.
computer-use-mcp
Control your computer with screenshots, mouse, and keyboard automation. Runs locally from the computer-use-mcp npm package.