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/BloomFilter-Labs/mcp-server-bloomfilterWrote 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/bloomfilter-labs/mcp-server-bloomfilter/bloomfilter)<a href="https://agentmods.dev/mcp/bloomfilter-labs/mcp-server-bloomfilter/bloomfilter"><img src="https://agentmods.dev/badge/mcp/bloomfilter-labs/mcp-server-bloomfilter/bloomfilter/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/bloomfilter-labs/mcp-server-bloomfilter/bloomfilter"><img src="https://agentmods.dev/badge/mcp/bloomfilter-labs/mcp-server-bloomfilter/bloomfilter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
bloomfilter 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 1mo 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
{
"bloomfilter": {
"command": "npx",
"args": [
"-y",
"@bloomfilter/mcp-server"
],
"env": {
"BLOOMFILTER_PRIVATE_KEY": "",
"BLOOMFILTER_API_URL": "",
"BLOOMFILTER_NETWORK": ""
}
}
}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.
- 1mo ago First seen · 14 lines scan A 0bf2c64d880f
bloomfilter is an MCP server published in the GitHub repository BloomFilter-Labs/mcp-server-bloomfilter (10 stars, last pushed 7mo ago), 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-08-31.
Other mcp servers, from other repositories
cinderwright-api
Cross-protocol agent payments hub. x402, MPP, L402/Lightning. 1551 services indexed. Runs locally from the cinderwright-mcp-server npm package.
dns-mcp
Model Context Protocol server for DNS, WHOIS, and IP geolocation lookups. Runs locally from the dns-mcp Python package.
glitchtip
MCP server "glitchtip", hosted remotely at glitchtip.infra.developerz.ai, as configured in developerz-ai/ai-task-master.
kura
MCP server "kura" as configured in dinggi5/kura. Launched with ./mcpb/server/kura-mcp.
weekly-review
MCP server "weekly-review", hosted remotely at 161.35.96.7, as configured in Vrooli/Vrooli.
domain-security-mcp-server
Audit a domain's email and web security: SPF, DKIM, DMARC, MTA-STS, DNSSEC, TLS, WHOIS. No API keys. Runs locally from the domain-security-mcp-server npm package.