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/figuard/figuard-coreWrote 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/figuard/figuard-core/mcp-figuard-mcp)<a href="https://agentmods.dev/mcp/figuard/figuard-core/mcp-figuard-mcp"><img src="https://agentmods.dev/badge/mcp/figuard/figuard-core/mcp-figuard-mcp/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/figuard/figuard-core/mcp-figuard-mcp"><img src="https://agentmods.dev/badge/mcp/figuard/figuard-core/mcp-figuard-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
figuard-mcp 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 2mo 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 2mo ago First seen · 15 lines scan A f0fbabc3f14e
figuard-mcp is an MCP server published in the GitHub repository figuard/figuard-core (2 stars, last pushed 1mo ago), with no licence file. 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
strands-docs
A Model Context Protocol server that provides knowledge about building AI agents with Strands Agents. Runs locally from the strands-agents-mcp-server Python package.
stipend
Non-custodial USDC wallet on Base with spending limits enforced in code, not in a prompt. Runs locally from the stipend npm package.
x402-payment-safety
Authorize x402 payments before signing with request-bound, signed safety decisions. Remote server at agent-guild-5d5r.onrender.com.
agentpay
Buyer-side trust oracle + capped sessions for x402 agents: verifiedroute, receipts, 17 free tools. Runs locally from the @romudille/agentpay-mcp npm package. Needs 3 environment variables to run.
agentpay
AgentPay — the economic-intelligence layer for AI agents: budget-capped tool calls with verifiable receipts, plus verifiedroute buyer-side x402 trust routing. 17 tools free to start, no keys; set AGENTPAYBASEKEY to settle paid tools in-place (gasless E. Runs locally from the @romudille/agentpay-mcp npm package.
alpaca-guard
Alpaca trading API with hard daily USD cap guard. Paper trading default; live opt-in. Runs locally from the alpaca-guard-mcp npm package. Needs 2 environment variables to run.