mcpbeat

Compliance Evidence MCP Server

com.dropwatchhq/compliance-evidence
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 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
69 ms
Response time
average over 24h
open, no key
Access
streamable-http

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.

run in your terminal
claude mcp add compliance-evidence --transport http https://evidence.dropwatchhq.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "compliance-evidence": {
      "url": "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
{
  "mcpServers": {
    "compliance-evidence": {
      "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

URLTransportStateLatencyChecked
https://evidence.dropwatchhq.com/mcp streamable-http answering 72 ms 10 min ago

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 69 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 with the file path 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 69 ms on average, which is faster than 94% 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.