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/ovbslaught/NOMADZ-0Wrote 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/ovbslaught/nomadz-0/firecrawl)<a href="https://agentmods.dev/mcp/ovbslaught/nomadz-0/firecrawl"><img src="https://agentmods.dev/badge/mcp/ovbslaught/nomadz-0/firecrawl/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/ovbslaught/nomadz-0/firecrawl"><img src="https://agentmods.dev/badge/mcp/ovbslaught/nomadz-0/firecrawl.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade 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 yesterday.
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
{
"firecrawl": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mendableai/firecrawl-mcp-server"
],
"env": {
"FIRECRAWL_API_KEY": "${FIRECRAWL_API_KEY}"
}
}
}What else mcp.json configures
This page is one entry in a file that holds 6. 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.
- yesterday First seen · 13 lines scan A 8a0efe96c09f
firecrawl is an MCP server published in the GitHub repository ovbslaught/NOMADZ-0 (5 stars, last pushed yesterday), 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-10-06.
Other mcp servers, from other repositories
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.
godot
The most complete Godot 4 MCP: secure sandbox, 40+ tools (projects–runtime), major MCP clients. Runs locally from the godot-mcp-server Python package.
godot-mcp-server
MCP server for Godot game engine integration. Runs locally from the godot-mcp-server 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-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.
chrome-tabs
MCP server "chrome-tabs" as configured in pokutuna/mcp-chrome-tabs. Runs src/cli.ts with node.