# com.dropwatchhq/compliance-evidence (remote · evidence.dropwatchhq.com)

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

- Trust score: 53/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `evidence.dropwatchhq.com`: 53/100 (this document), [markdown](https://verifymcp.io/servers/com-dropwatchhq-compliance-evidence/evidence.md), [page](https://verifymcp.io/servers/com-dropwatchhq-compliance-evidence/evidence)

## Channel facts

- Endpoint: `https://evidence.dropwatchhq.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 402 tokens (~100/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 78/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 33% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.com-dropwatchhq-compliance-evidence]
url = "https://evidence.dropwatchhq.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-dropwatchhq-compliance-evidence": {
      "type": "remote",
      "url": "https://evidence.dropwatchhq.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-dropwatchhq-compliance-evidence --url https://evidence.dropwatchhq.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-dropwatchhq-compliance-evidence:
    url: "https://evidence.dropwatchhq.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-dropwatchhq-compliance-evidence": {
      "type": "http",
      "url": "https://evidence.dropwatchhq.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 53, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 52, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 52, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 51, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 50, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 49)

First indexed and scored.

## MCP tools (4)

### `build_evidence_pack` (~196 tokens)

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.

Input parameters:

- `entities` (array): Named entities to screen: [{name, npi?, uei?, state?}] (max 20).
- `tickers` (array): Public-company tickers whose disclosure claims to ground (max 10).
- `traps` (array): Optional custom trap-fact battery; omit to use the default battery.

### `ground_claim` (~74 tokens)

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.

Input parameters:

- `ticker` (string, required)

### `screen_entity` (~90 tokens)

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.

Input parameters:

- `name` (string, required)
- `npi` (string)
- `state` (string)
- `uei` (string)

### `verify_pack` (~42 tokens)

Verify a previously-issued pack's hash-chain receipt (proves the artifact is unaltered since generatedAt). Pass the pack id.

Input parameters:

- `id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-dropwatchhq-compliance-evidence/evidence#diagnostics

## Score history

- 2026-08-03: 53
- 2026-08-02: 53
- 2026-08-01: 52
- 2026-07-31: 52
- 2026-07-30: 52
- 2026-07-29: 51
- 2026-07-28: 51
- 2026-07-27: 50
- 2026-07-26: 49

## Links

- Remote endpoint: https://evidence.dropwatchhq.com/mcp
- Website: https://evidence.dropwatchhq.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-dropwatchhq-compliance-evidence/evidence/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-dropwatchhq-compliance-evidence/evidence/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-dropwatchhq-compliance-evidence/evidence