mcp server
compliance-evidence
Dated, signed compliance-evidence packs: gov-fact-grounded claims + exclusion screens + trap-facts.
Description as published by the maintainer. Source
- version 1.0.0
- active
- security
active — Registry entry last updated 2026-06-22. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
build_evidence_pack(traps, tickers, entities)- 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_claim(ticker)- 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. Required: ticker.
screen_entity(npi, uei, name, state)- 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. Required: name.
verify_pack(id)- Verify a previously-issued pack's hash-chain receipt (proves the artifact is unaltered since generatedAt). Pass the pack id. Required: id.
Last successful function declaration observed on . Source: https://evidence.dropwatchhq.com/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://evidence.dropwatchhq.com/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-22 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-22 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 4 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | evidence.dropwatchhq.com | |
| mcp endpoint status | ok | The server listed 4 functions when asked. | as of probe | evidence.dropwatchhq.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json