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/LeonTing1010/tapWrote 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/leonting1010/tap/mcp-tap)<a href="https://agentmods.dev/mcp/leonting1010/tap/mcp-tap"><img src="https://agentmods.dev/badge/mcp/leonting1010/tap/mcp-tap/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/leonting1010/tap/mcp-tap"><img src="https://agentmods.dev/badge/mcp/leonting1010/tap/mcp-tap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tap 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 1mo 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
{
"tap": {
"command": "npx",
"args": [
"-y",
"@taprun/cli",
"mcp",
"stdio"
],
"env": {}
}
}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.
- 1mo ago First seen · 12 lines scan A b19cf9148a7c
tap is an MCP server published in the GitHub repository LeonTing1010/tap (18 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-30.
Other mcp servers, from other repositories
stagehand
MCP server "stagehand" as configured in browserbase/stagehand. Runs ../core/dist/facade/stdio-server.mjs with node.
browser-mcp
Browser MCP - the browser tool that can stop and ask you. A 2FA code, a CAPTCHA, a choice only you can make: it asks on your own screen, then carries on in the tab you were already signed into. 40 tools, any MCP client, MIT. Runs locally from the @agent360/browser-mcp npm package.
real-browser
MCP server + Chrome extension for AI browser control with real sessions. Runs locally from the real-browser-mcp npm package.
fortress
Open stealth-browser framework — drive a real recompiled-Chromium (Fortress) that defeats bot-detection fingerprint suites. Drop-in stealth for browser-use, Playwright, Crawl4AI, with an MCP server for AI agents. Runs locally from the tilion Python package. Needs 5 environment variables to run.
browser-controller
Control your browser. Runs locally from the browser-controller npm package.
chrome-bridge
Your real, logged-in Chrome as an MCP server: 60 token-efficient web-dev tools. ChromeOS included. Runs locally from the chrome-bridge-mcp npm package.