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/Anandb71/BleursWrote 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/anandb71/bleurs/bleurs)<a href="https://agentmods.dev/mcp/anandb71/bleurs/bleurs"><img src="https://agentmods.dev/badge/mcp/anandb71/bleurs/bleurs/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/anandb71/bleurs/bleurs"><img src="https://agentmods.dev/badge/mcp/anandb71/bleurs/bleurs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
bleurs 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
{ "bleurs": { "command": "uvx", "args": [ "bleurs" ] } }
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 · 8 lines scan A 8a13e3ce3f43
bleurs is an MCP server published in the GitHub repository Anandb71/Bleurs (0 stars, last pushed 2mo 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
honestcode
A lightweight MCP server that detects AI code hallucinations in real time — undefined symbols, wrong API calls, dead code, and type mismatches. Runs locally from the honestcode Python package.
factanchor-mcp
MCP server "factanchor-mcp" as configured in Tausifonly001/FactAnchor-MCP. Runs locally from the factanchor-mcp Python package.
grounded-reasoning
Zero-token, precision-guaranteed verifier for LLM/agent multi-hop relational reasoning. Runs locally from the grounded-reasoning Python package.
verifiable-memory
Verifiable memory for AI agents — 0% hallucination, cited, provably forgettable, deterministic. MCP server. CPU-only, no GPU, zero dependencies. Runs locally from the verifiable-memory-mcp Python package.
vaporcheck
MCP server "vaporcheck" as configured in cdmx-in/vaporcheck. Launched with py -3 c:/Users/Roney/Documents/new-project/vaporcheck/server.py.
swiss-transport-mcp
MCP server for Swiss public transport – OJP journey planner, real-time departures, disruptions, occupancy, ticket prices, train formations and open data from opentransportdata.swiss. Runs locally from the swiss-transport-mcp Python package.