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/BitBadges/bitbadges-builder-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/bitbadges/bitbadges-builder-mcp/bitbadges-builder-mcp)<a href="https://agentmods.dev/mcp/bitbadges/bitbadges-builder-mcp/bitbadges-builder-mcp"><img src="https://agentmods.dev/badge/mcp/bitbadges/bitbadges-builder-mcp/bitbadges-builder-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
bitbadges-builder-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 7d 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
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 7d ago First seen · 9 lines scan A a130bdb53b7d
bitbadges-builder-mcp is an MCP server published in the GitHub repository BitBadges/bitbadges-builder-mcp (0 stars, last pushed 4mo 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
agentwallet
Wallet infrastructure for Ai agents. EVM + Solana. x402 payments. No KYC. Runs locally from the agentwallet-mcp npm package. Needs 1 environment variable to run.
verdoc-mcp
MCP server "verdoc-mcp" as configured in verdochello/verdoc-mcp. Launched with https://github.com/verdochello/verdoc-mcp/releases/download/v0.1.0/verdoc-mcp-0.. Needs 2 environment variables to run.
anchor-mcp
Generate MCP tools from any Solana Anchor program's IDL — let AI agents read & simulate its instructions with zero per-program code. Runs locally from the anchor-mcp npm package.
agent-gateway
Thirty-one guarded pay-per-call preflights and evidence products over USDC x402. Runs locally from the @justhandledlabs/agent-client npm package. Needs 1 environment variable to run.
furlpay-cli
Stablecoin payments, swaps, stock orders, market data, travel booking, yield and card controls. Runs locally from the @furlpay/cli npm package.
mcp
Validator incident data for AI agents across Solana, Ethereum, Sui, and Cosmos. Remote server at mcp.slashr.dev.