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/fidacy-payment-firewall-fidacy)<a href="https://agentmods.dev/mcp/lucaslubi/fidacy-mcp/fidacy-payment-firewall-fidacy"><img src="https://agentmods.dev/badge/mcp/lucaslubi/fidacy-mcp/fidacy-payment-firewall-fidacy/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/fidacy-payment-firewall-fidacy"><img src="https://agentmods.dev/badge/mcp/lucaslubi/fidacy-mcp/fidacy-payment-firewall-fidacy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
fidacy 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
{
"fidacy": {
"command": "npx",
"args": [
"-y",
"@fidacy/mcp"
]
}
}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 · 9 lines scan A 187d532f360c
fidacy 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
bitcoin-mcp
MCP server for Bitcoin — 49 tools for AI agents to save money on fees. Zero config, works out of the box. Runs locally from the bitcoin-mcp Python package.
btc-node
Real BTC full node: fees, mempool, txs, portfolio, trace, whales, SEC, scraping, Reddit via x402. Remote server at mcp.btcnode.uk.
brs-signals-mcp
Live Bitcoin market regime for agents: three sensors read pre-price data — fee curves, funding velocity, whale flows, absence — every 30s and reject almost everything. When they converge, a directional call is emitted with evidence. The data can't be reconstructed from history. Public, agent-auditable track record.…
d365fo-client
Microsoft Dynamics 365 Finance & Operations client and MCP server. Runs locally from the d365fo-client Python package. Needs 4 environment variables to run.
lunchmoney-mcp
MCP server for managing LunchMoney personal finances: transactions, budgets, categories, and more. Runs locally from the @akutishevsky/lunchmoney-mcp npm package. Needs 2 environment variables to run.
yahoo-finance-mcp
Real-time Yahoo Finance data: quotes, history, financials, analyst ratings, options, and news. Runs locally from the yahoo-finance-mcp-server npm package.