Skip to content

compliance-evidence MCP server

com.dropwatchhq/compliance-evidencedropwatchhq.comstreamable-httpv1.0.0Scanned

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

4 tools: 4 change things.

Tools: 0 delete, 0 irreversible, 4 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the compliance-evidence MCP server can do

The compliance-evidence MCP server is published by dropwatchhq.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (4 tools: build_evidence_pack, ground_claim, screen_entity and verify_pack), but cannot delete data. None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 17, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 4Claude Code: ask
  • build_evidence_packBuild a dated, source-linked, SIGNED compliance-evidence pack for a regulated-AI deployer to file with their auditor.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_claimGround one public-company claim against CURRENT gov facts via the live contradiction-engine.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_entityScreen a named entity across federal exclusion/sanctions lists (OFAC SDN, OFAC Consolidated, OIG LEIE; SAM where enabled) via the live exclude-feed.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_packVerify a previously-issued pack's hash-chain receipt (proves the artifact is unaltered since generatedAt).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Verify a previously-issued pack's hash-chain receipt (proves the artifact is unaltered since generatedAt). Pass the pack id.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:24 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://evidence.dropwatchhq.com/mcp: tools/list returned 4 tools to an anonymous client, including build_evidence_pack (write), ground_claim (write), screen_entity (write), verify_pack (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__compliance-evidence__build_evidence_pack",
      "mcp__compliance-evidence__ground_claim",
      "mcp__compliance-evidence__screen_entity",
      "mcp__compliance-evidence__verify_pack"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as compliance-evidence. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.dropwatchhq/compliance-evidence/verify?hash=3d76b2f417a847ccb9c90acbb69164e6842c7068551f4818c742b7ee5f01bd93" | jq -e '.changed == false'

Pinned hash 3d76b2f417a8, from Nov 17, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.dropwatchhq/compliance-evidence/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.dropwatchhq/compliance-evidence
[![Anlyon Radar](https://radar.anlyon.com/badge/com.dropwatchhq/compliance-evidence.svg)](https://radar.anlyon.com/servers/com.dropwatchhq/compliance-evidence)

Source: MCP Registry. Synced Oct 21, 2026, 17:54 UTC.

compliance-evidence MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the compliance-evidence MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the compliance-evidence MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the compliance-evidence MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the compliance-evidence MCP server have?

4 tools: 4 write. build_evidence_pack, ground_claim, screen_entity and verify_pack.

Does the compliance-evidence MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the compliance-evidence MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the compliance-evidence MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.