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/HemmaBo-se/hemmabo-mcp-serverWrote 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/hemmabo-se/hemmabo-mcp-server/hemmabo)<a href="https://agentmods.dev/mcp/hemmabo-se/hemmabo-mcp-server/hemmabo"><img src="https://agentmods.dev/badge/mcp/hemmabo-se/hemmabo-mcp-server/hemmabo/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/hemmabo-se/hemmabo-mcp-server/hemmabo"><img src="https://agentmods.dev/badge/mcp/hemmabo-se/hemmabo-mcp-server/hemmabo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
hemmabo 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.
What it actually says
{
"hemmabo": {
"type": "http",
"url": "https://www.hemmabo.com/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.
- 2mo ago First seen · 6 lines scan A 691ff03f71d5
hemmabo is an MCP server published in the GitHub repository HemmaBo-se/hemmabo-mcp-server (4 stars, last pushed yesterday), 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
mcp-server
Check the reputation of AI microservices and public APIs from an open trust registry. Runs locally from the @trustscoreagent/mcp-server npm package. Needs 2 environment variables to run.
server-attestation
Ed25519-signed MCP tool manifests + spawn attestation. Layer-2 supply-chain hardening. Runs locally from the mcp-attest-demo npm package.
bft-progress-council-mcp
BFT Progress Council MCP — 5-voter Byzantine council halts agentic loops when no real progress is happening. Stops tokens bleeding on infinite spins. By MEOK AI Labs. Runs locally from the bft-progress-council-mcp Python package.
aga-mcp-server
Verifiable decision records for AI agents: signed receipts for calls to its own governed tools. Runs locally from the @attested-intelligence/aga-mcp-server npm package. Needs 2 environment variables to run.
council-signal-mcp
Signed AI measurement (13-axis, deterministic judge). Measurement, not certification; monitored containment; UNMEASURED is never wrong. Runs locally from the council-signal-mcp Python package.
ai-agent-firewall
Every agent action watched, every money-moving one gated, every verdict independently verifiable. Runs locally from the @fidacy/mcp npm package. Needs 3 environment variables to run.