Compliance Evidence MCP Server

by dropwatchhq Your server? Claim it

answering

Compliance Evidence is answering right now. Last checked 10 min ago. It exposes 4 tools.

Dated, signed compliance-evidence packs: gov-fact-grounded claims + exclusion screens + trap-facts.

Uptime history 91 days of history · worst day 93%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

96 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Compliance Evidence every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add compliance-evidence --transport http https://evidence.dropwatchhq.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://evidence.dropwatchhq.com/mcp

~/.codex/config.toml

[mcp_servers.compliance-evidence]
url = "https://evidence.dropwatchhq.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "compliance-evidence": {
      "url": "https://evidence.dropwatchhq.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "compliance-evidence": {
      "type": "http",
      "url": "https://evidence.dropwatchhq.com/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

build

build_evidence_pack

Build a dated, source-linked, SIGNED compliance-evidence pack for a regulated-AI deployer to file with their auditor. Grounds each ticker's claims against CURRENT public gov facts (contradiction-engine: SEC 10-K vs USAspending), screens each named entity against federal exclusion/sanctions (exclude-feed: OFAC/LEIE/SAM), and runs N trap-fact refusals (planted false facts refuted by live public data). Output is an EVIDENCE ARTIFACT with a hash-chain receipt — NOT a 'you are compliant' claim.

ground

ground_claim

Ground one public-company claim against CURRENT gov facts via the live contradiction-engine. Returns the dual-cited record if a verifiable 10-K-vs-USAspending contradiction exists, else an HONEST null ('checked, no contradiction at medium/high confidence as of T') — itself audit evidence.

screen

screen_entity

Screen a named entity across federal exclusion/sanctions lists (OFAC SDN, OFAC Consolidated, OIG LEIE; SAM where enabled) via the live exclude-feed. FCRA-safe KYB/sanctions screen, not a consumer report.

verify

verify_pack

Verify a previously-issued pack's hash-chain receipt (proves the artifact is unaltered since generatedAt). Pass the pack id.

Endpoints

URL	Transport	State	Latency	Checked
https://evidence.dropwatchhq.com/mcp	streamable-http	answering	56 ms	10 min ago

Alternatives to Compliance Evidence

same job, measured the same way

Prove It

by ark-forge

Free public benchmark for AI agents: compliance tasks, every claim checked against signed receipts

85 installs/wk local only

Health Intel

by dropwatchhq

Healthcare provider & compliance intel: NPPES lookup, OIG/SAM exclusion screening, FDA enforcement.

4 tools answering

EU Audit Trail

by jellewas

Tamper-evident audit trail MCP server for EU AI Act & GDPR compliance.

92 installs/wk local only

LION — Verified Company & Compliance Data

by lionx402

Keyless x402 compliance on Base: $0.001 OFAC wallet screen, $0.05 pack, $0.95 company file.

37 tools answering

21RISK

by 21risk

Read and update your 21RISK data: sites, audits, compliance, actions, claims and insurance values.

answering

Verity

by veritylabsai

Cited product-compliance ground truth for AI agents. Never generates; always cites.

4 tools answering

Compliance AIops

by aiops-tools

Compliance evidence from AIops audit trails: HIPAA/PCI/SOC2/GDPR, OSCAL export, 19 tools.

607 installs/wk local only

MCP x402 - Evidence-Backed Web Verification

by diogoup26

Evidence-backed pre-purchase checks for offer terms, seller trust and policy compliance.

4 tools answering

Compliance Evidence — questions

Answers built from our own checks of this server.

What can Compliance Evidence do?

It exposes 4 tools, read directly from the server on our last check. Among them: build_evidence_pack, ground_claim, screen_entity, verify_pack. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Compliance Evidence working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 96 ms. The bar chart above shows every period we have measured.

How do I connect Compliance Evidence?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Compliance Evidence need an API key?

No. Compliance Evidence completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Compliance Evidence?

It answers our handshake in 96 ms on average, which is faster than 93% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.