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/median-labs/median-compliance-skillWrote 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/median-labs/median-compliance-skill/compliance)<a href="https://agentmods.dev/mcp/median-labs/median-compliance-skill/compliance"><img src="https://agentmods.dev/badge/mcp/median-labs/median-compliance-skill/compliance/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/median-labs/median-compliance-skill/compliance"><img src="https://agentmods.dev/badge/mcp/median-labs/median-compliance-skill/compliance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
compliance 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 12d 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
{
"compliance": {
"url": "https://medianfi.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.
- 12d ago First seen · 6 lines scan A d9479ee5331e
compliance is an MCP server published in the GitHub repository median-labs/median-compliance-skill (3 stars, last pushed 22d 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
compliance
MiCA compliance evidence, stablecoin risk, macro regime, agent governance. 79 tools. Remote server at feedoracle.io.
openaccountants-mcp
MCP server for OpenAccountants tax skills. Runs locally from the openaccountants-mcp Python package.
eu-ai-act-mcp
EU AI Act compliance MCP server with bounded system assessment, structured classification, article grounding, GPAI, Art. 6(3), Annex III/IV, deadlines, obligations, penalties, and FAQ. By Lexbeam Software. Runs locally from the @lexbeam-software/eu-ai-act-mcp npm package.
mcp-quipu
Quipu API integration with 18 MCP tools for invoices, expenses, contacts and Spanish VAT reporting. Runs locally from the @nubiia/mcp-quipu npm package. Needs 3 environment variables to run.
mcp-holded
MCP server for the Holded API v2 (Bearer auth): contacts, invoices, purchases, products, services, payments, plus a generic request tool for any v2 endpoint. Runs locally from the @t4dhg/mcp-holded npm package. Needs 5 environment variables to run.
vat-validator-mcp
Validate EU, UK, AU VAT numbers for AI agents. EU ViDA e-invoicing compliance. Runs locally from the vat-validator-mcp npm package. Needs 3 environment variables to run.