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/holistis/al-yadWrote 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/holistis/al-yad/yad-agent-mcp)<a href="https://agentmods.dev/mcp/holistis/al-yad/yad-agent-mcp"><img src="https://agentmods.dev/badge/mcp/holistis/al-yad/yad-agent-mcp/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/holistis/al-yad/yad-agent-mcp"><img src="https://agentmods.dev/badge/mcp/holistis/al-yad/yad-agent-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
yad-agent-mcp 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 12d 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
{ "yad-agent-mcp": { "command": "npx", "args": [ "-y", "yad-agent-mcp" ], "env": { "YAD_COMPANION_URL": "http://127.0.0.1:3747" } } }
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.
- 12d ago First seen · 12 lines scan A cc64471c3260
yad-agent-mcp is an MCP server published in the GitHub repository holistis/al-yad (4 stars, last pushed today), 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
real-browser
MCP server + Chrome extension for AI browser control with real sessions. Runs locally from the real-browser-mcp npm package.
browser-mcp
Browser MCP — control your real Chrome from Claude Code. 34 tools, CAPTCHA solving, date pickers, autocomplete combobox, overlay dismissal, file upload, multi-session, human-in-the-loop. Runs locally from the @agent360/browser-mcp npm package.
browser-mcp
MCP server "browser-mcp" as configured in EndymionLee/PilotBrowseMCP. Runs BrowserPlugin\server\dist\index.js with node.
pixelcheck
Real eyes and hands on the web for AI agents. MCP-first. Local-first. Vendor-agnostic. Runs locally from the pixelcheck npm package. Needs 1 environment variable to run.
sidebutton
Open-source MCP server with browser automation and knowledge packs for AI agents. Runs locally from the @sidebutton/server npm package.
tap
Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay. Runs locally from the @taprun/cli npm package.