DropWatch Compliance Evidence MCP MCP server

An MCP server that generates dated, signed compliance-evidence packs grounded in public-source data. It allows agents to build evidence packs for tickers and entities, ground specific claims, screen entities, and verify the cryptographic integrity of receipts using hash-chains. The service returns honest nulls for unverified data and supports payment via x402/EIP-3009.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by DropWatch HQ

MCP endpoint (Streamable HTTP)

https://evidence.dropwatchhq.com/mcp

Vendor documentation

What you can do with it

Build signed evidence packs for specific tickers and corporate entities
Ground a single claim live against public sources
Screen an entity for compliance-related facts
Verify the cryptographic receipt of a generated evidence pack

Tools advertised by the last live check:

build_evidence_pack
ground_claim
screen_entity
verify_pack

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

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

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add dropwatch-compliance-evidence-mcp --url https://evidence.dropwatchhq.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable dropwatch-compliance-evidence-mcp in your MCP settings.

Cursor configuration

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

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "dropwatch-compliance-evidence-mcp": {
      "type": "streamableHttp",
      "url": "https://evidence.dropwatchhq.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start dropwatch-compliance-evidence-mcp and inspect its tools.

VS Code configuration

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

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

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

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

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

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

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

See all 1,583

Do you run DropWatch Compliance Evidence MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing