Builds dated, signed compliance-evidence packs that ground company claims against current government facts and screen entities against federal exclusion lists.
What you can do
The server exposes four tools. build_evidence_pack produces a dated, source-linked, signed evidence pack for a regulated-AI deployer to file with an auditor, grounding each ticker's claims against current public government facts and screening named entities. ground_claim checks one public-company claim against live government facts and returns a dual-cited record or an explicit no-contradiction result. screen_entity screens a named entity across federal exclusion and sanctions lists. verify_pack checks a previously issued pack's hash-chain receipt to show it is unaltered.
When to use it
Use it when preparing audit or compliance documentation for regulated AI deployments, when you need to check a public-company claim against government sources, or when you need a sanctions or exclusion screen on a named entity before filing.
Requirements
A remote streamable HTTP endpoint at evidence.dropwatchhq.com; no packages, environment variables or headers are declared. Network access to the endpoint is required.
Before you install
Packs are signed and hash-chained, so treat generated artifacts as formal records. Screening results are described as FCRA-safe KYB/sanctions screening, not consumer reports, and should not be used as such. Claims and entity names you submit are sent to a third-party service.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.dropwatchhq%2Fcompliance-evidence/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
Parameterstrapstickersentities
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.
Parameterstickerrequired
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.
Parametersnpiueinamerequiredstate
verify_pack
Verify a previously-issued pack's hash-chain receipt (proves the artifact is unaltered since generatedAt). Pass the pack id.
Parametersidrequired
Version history
1
v1.0.0LatestSep 16, 2026
Score
72%
72% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.