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/lucaslubi/fidacy-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/lucaslubi/fidacy-mcp/ai-agent-firewall)<a href="https://agentmods.dev/mcp/lucaslubi/fidacy-mcp/ai-agent-firewall"><img src="https://agentmods.dev/badge/mcp/lucaslubi/fidacy-mcp/ai-agent-firewall/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/lucaslubi/fidacy-mcp/ai-agent-firewall"><img src="https://agentmods.dev/badge/mcp/lucaslubi/fidacy-mcp/ai-agent-firewall.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ai-agent-firewall 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 10d 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
{
"ai-agent-firewall": {
"command": "npx",
"args": [
"-y",
"@fidacy/mcp"
],
"env": {
"FIDACY_ENGINE_API_KEY": "",
"FIDACY_OPERATOR_EMAIL": "",
"FIDACY_MODE": ""
}
}
}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.
- 10d ago First seen · 14 lines scan A 0d3259237418
ai-agent-firewall is an MCP server published in the GitHub repository lucaslubi/fidacy-mcp (1 stars, last pushed 1mo ago), licensed Apache-2.0. 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
hemmabo
MCP server "hemmabo", hosted remotely at www.hemmabo.com, as configured in HemmaBo-se/hemmabo-mcp-server.
hemmabo-mcp-server
Host-owned vacation-rental direct booking via VRP. Signed offers, 0% commission. Not an OTA. Remote server at www.hemmabo.com.
otskit-mcp
Stamp, upgrade, and verify Bitcoin timestamps via AI agents. No API keys required. Runs locally from the @otskit/mcp npm package.
ordinals
Bitcoin Ordinals MCP Server — inscriptions, runes, BRC-20, collections & rare sats. Runs locally from the ordinals-mcp npm package. Needs 3 environment variables to run.
sophos-firewall-mcp-server
MCP server "sophos-firewall-mcp-server" as configured in jelmervdm/sophos-firewall-mcp. Runs locally from the sophos-firewall-mcp-server Python package.
netdefense-mcp
MCP server "netdefense-mcp" as configured in netdefense-io/NDCLI. Launched with https://github.com/netdefense-io/ndcli-releases/releases/download/v1.29.2/netdef. Needs 1 environment variable to run.