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/viknesh20-20/claude-code-tool-kit/firecrawlgit clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-kitGrade A, and why
firecrawl 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 3d 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.
This is a copy
100% identical to firecrawl — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"firecrawl": {
"command": "npx",
"args": [
"-y",
"firecrawl-mcp"
],
"env": {
"FIRECRAWL_API_KEY": "${FIRECRAWL_API_KEY}"
}
}
}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.
- 3d ago First seen · 12 lines scan A 6277f95ec375
firecrawl is an MCP server published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 4mo 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. It is 100% identical to firecrawl, differing in 0 lines, and is treated as a copy.
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.
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.
chrome-enterprise-premium-mcp
Chrome Enterprise Premium MCP server. Runs locally from the @google/chrome-enterprise-premium-mcp npm package.
crow
a remote URL tester for the terminal. Runs locally from the crow npm package.
evomi-mcp
MCP server for the Evomi proxy and web scraping APIs. Runs locally from the evomi-mcp Python package.
dawg
MCP server for the DAWG platform — remote stealth browser, scraping & account usage for AI agents. Built for Runet: Russian residential proxies and geolocation. Runs locally from the dawg-mcp Python package. Needs 2 environment variables to run.