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/feedoracle/feedoracle-managed-agentsWrote 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/feedoracle/feedoracle-managed-agents/compliance)<a href="https://agentmods.dev/mcp/feedoracle/feedoracle-managed-agents/compliance"><img src="https://agentmods.dev/badge/mcp/feedoracle/feedoracle-managed-agents/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/feedoracle/feedoracle-managed-agents/compliance"><img src="https://agentmods.dev/badge/mcp/feedoracle/feedoracle-managed-agents/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 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
{
"compliance": {
"url": "https://feedoracle.io/mcp/sse",
"type": "sse"
}
}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 · 6 lines scan A 338e22cd04b7
compliance is an MCP server published in the GitHub repository feedoracle/feedoracle-managed-agents (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
compliance
US company filing obligations, plus a 25-check bookkeeping diagnostic. Sourced, dated, no signup. Remote server at medianfi.com.
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.
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.
bagos
MCP server for Bags on Solana: token analytics, trade quotes, and gated write operations. Runs locally from the bagos-mcp-server npm package. Needs 11 environment variables to run.
iso20022-evidence-pack-mcp
MCP server that compiles ISO 20022 readiness findings, remediation diffs, and simulated responses into sealed audit evidence packs. Runs locally from the iso20022-evidence-pack-mcp Python package.
opdstar-nhi
The MCP server for Taiwan NHI billing intelligence — rejection codes, audit clauses, drug payment rules, fee schedule, special materials, and appeal case precedents. Helps AI agents answer Taiwan health-insurance billing and audit questions with authorita. Runs locally from the @opdstar/nhi-mcp npm package.