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/j-sulliman/hopgraph-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/j-sulliman/hopgraph-mcp/hopgraph)<a href="https://agentmods.dev/mcp/j-sulliman/hopgraph-mcp/hopgraph"><img src="https://agentmods.dev/badge/mcp/j-sulliman/hopgraph-mcp/hopgraph/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/j-sulliman/hopgraph-mcp/hopgraph"><img src="https://agentmods.dev/badge/mcp/j-sulliman/hopgraph-mcp/hopgraph.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
hopgraph 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 9d 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
{
"hopgraph": {
"url": "https://hopgraph.com/mcp/",
"type": "streamable-http"
}
}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.
- 9d ago First seen · 6 lines scan A 9b1e59abfc6a
hopgraph is an MCP server published in the GitHub repository j-sulliman/hopgraph-mcp (0 stars, last pushed 6mo 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
sanctions-screening-mcp-server
Screen names against OFAC, EU, UK, UN sanctions lists; resolve entities via GLEIF. Screening aid. Runs locally from the @cyanheads/sanctions-screening-mcp-server npm package. Needs 4 environment variables to run.
mcp-fns-check
MCP server for checking RU counterparties via FNS open data (EGRUL/EGRIP, EFRSB, KAD, FSSP). Runs locally from the atomno-mcp-fns-check Python package.
tender-mcp
Government tender search for AI agents. UK, EU and US procurement opportunities. Runs locally from the tender-mcp npm package. Needs 1 environment variable to run.
sanctionwise
Verified UK sanctions screening for AI agents — official FCDO UK Sanctions List, not guesses. Runs locally from the sanctionwise npm package.
nordic-data
Company, KYB, VAT, sanctions, LEI and address data for 15 EU countries. Runs locally from the nordic-data-mcp npm package. Needs 3 environment variables to run.
australian-ai-governance-framework
Australian AI governance framework mapped to the Privacy Act and sector laws your AI use triggers. Remote server at aiframework.com.au.