# Compliance Check (remote · hatchloop.dev)

Preview a TCPA/GDPR/CASL/10DLC gate result before spending a paid send. No key needed.

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- remote · `hatchloop.dev`: 82/100 (this document), [markdown](https://verifymcp.io/servers/dev-hatchloop-compliance-check/mcp-compliance-check.md), [page](https://verifymcp.io/servers/dev-hatchloop-compliance-check/mcp-compliance-check)

## Channel facts

- Endpoint: `https://hatchloop.dev/mcp/compliance-check`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.13`

## 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-09-22.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1461 tokens (~112/item across 13 items; 8 tools + 5 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Compliance Check MCP server?

Compliance Check is a hosted endpoint at https://hatchloop.dev/mcp/compliance-check, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-hatchloop-compliance-check 'https://hatchloop.dev/mcp/compliance-check'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-hatchloop-compliance-check": {
      "url": "https://hatchloop.dev/mcp/compliance-check"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-hatchloop-compliance-check": {
      "type": "http",
      "url": "https://hatchloop.dev/mcp/compliance-check"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-hatchloop-compliance-check]
url = "https://hatchloop.dev/mcp/compliance-check"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-hatchloop-compliance-check": {
      "type": "remote",
      "url": "https://hatchloop.dev/mcp/compliance-check",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-hatchloop-compliance-check --url 'https://hatchloop.dev/mcp/compliance-check' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-hatchloop-compliance-check:
    url: "https://hatchloop.dev/mcp/compliance-check"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-hatchloop-compliance-check": {
      "Transport": "http",
      "Url": "https://hatchloop.dev/mcp/compliance-check"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-hatchloop-compliance-check -t streamable-http -u 'https://hatchloop.dev/mcp/compliance-check'
```

### Other

```json
{
  "mcpServers": {
    "dev-hatchloop-compliance-check": {
      "type": "http",
      "url": "https://hatchloop.dev/mcp/compliance-check"
    }
  }
}
```

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-09-22 (score 82, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Schema quality: good → excellent

### 2026-09-21 (score 82, +1)

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

### 2026-09-19 (score 81, +1)

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

### 2026-09-17 (score 80, +1)

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

### 2026-09-15 (score 79, +1)

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

### 2026-09-12 (score 78, +1)

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

### 2026-09-11 (score 77, +3)

- [security] Tool “check_compliance” rewrote its description, which is the text the model reads
- [security] Tool “get_outcome” rewrote its description, which is the text the model reads
- [security] Tool “get_status” rewrote its description, which is the text the model reads
- [security] Tool “map_trade_restriction” rewrote its description, which is the text the model reads
- [security] Tool “preview_cost” rewrote its description, which is the text the model reads
- [security] Tool “screen_sanctions” rewrote its description, which is the text the model reads
- [security] Tool “self_test” rewrote its description, which is the text the model reads
- [security] Tool “verify_company_record” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: 294 → 109
- [cosmetic] “check_compliance” reworded the description of “channel”
- [cosmetic] “check_compliance” reworded the description of “content”
- [cosmetic] “check_compliance” reworded the description of “country_code”
- [cosmetic] “check_compliance” reworded the description of “message_type”
- [cosmetic] “map_trade_restriction” reworded the description of “destination_country”
- [cosmetic] “map_trade_restriction” reworded the description of “hs_code”
- [cosmetic] “map_trade_restriction” reworded the description of “origin_country”
- [cosmetic] “map_trade_restriction” reworded the description of “parties”
- [cosmetic] “map_trade_restriction” reworded the description of “product”
- [cosmetic] “screen_sanctions” reworded the description of “country”
- [cosmetic] “screen_sanctions” reworded the description of “name”
- [cosmetic] “screen_sanctions” reworded the description of “type”
- [cosmetic] “verify_company_record” reworded the description of “country”

### 2026-09-10 (score 74, −2)

- [security regression] HSTS header: pass → fail

## MCP tools (8)

### `get_status` (~36 tokens)

Query the current state of any in-flight async operation by operation_id. [free, no key]

Input parameters:

- `operation_id` (string, required)

### `get_outcome` (~33 tokens)

Retrieve the final OutcomeReceipt for a completed operation. [free, no key]

Input parameters:

- `operation_id` (string, required)

### `preview_cost` (~95 tokens)

Return an expected cost estimate, latency estimate, and success-probability estimate for a proposed call before execution. Returns the exact price when it is fixed, and a min/max range when the cost depends on channel or outcome. It does not promise an accuracy percentage - check cost_range. [free, no key]

Input parameters:

- `operation` (string, required)
- `params` (object, required): The same request body you would pass to the operation

### `self_test` (~54 tokens)

Service health probe: runs 6 internal checks and reports how many passed. Confirms the server is up and responding - it does NOT probe each tool individually. Use to verify connectivity before production use. [free, no key]

### `check_compliance` (~283 tokens)

Free, instant pre-flight for the compliance gate. Runs the SAME TCPA / GDPR / CASL / CAN-SPAM / 10DLC gate that send_message and call_business run — but in preview mode, so NO message is sent and NO state changes. Tells you whether a (recipient, channel, message_type, content) send would be permitted BEFORE you pay for it, and if not, names the exact rule and how to remediate. Use it to de-risk a paid send the same way check_booking_link… [free, no key]

Input parameters:

- `channel` (string): Delivery channel. Omit to auto-infer sms/email from recipient_id; set 'voice'…
- `content` (string, required): The actual message body you intend to send. The gate classifies the real text,…
- `country_code` (string): ISO 3166-1 alpha-2 (e.g. 'US', 'DE', 'CA'). Auto-inferred from phone if…
- `message_type` (string): Intent tag: transactional, marketing, reminder, follow_up, notification.…
- `recipient_id` (string, required): Phone in E.164 (e.g. '+14045550100') or email address the message would go to.
- `state_code` (string): US state code (e.g. 'CA') for state-specific rules.

### `verify_company_record` (~189 tokens)

Free, live lookup of a company official registry record. Queries the GLEIF global LEI registry (primary, 2.6 million legal entities worldwide) and SEC EDGAR (US public companies) to return the official legal name, LEI, entity status, jurisdiction, registered address, and registry authority. Never fabricates: if the company is not found in these free registries, returns an honest not_found with the sources that were queried. [free in quota, then $0.02/call]

Input parameters:

- `country` (string): Optional ISO 3166-1 alpha-2 country filter (e.g. US, DE, GB). Narrows GLEIF…
- `lei` (string): Optional 20-character Legal Entity Identifier for a direct, precise lookup.
- `name` (string, required): Legal company name to look up, e.g. Apple Inc or Volkswagen AG.

### `screen_sanctions` (~201 tokens)

Free screening of a name or entity against official sanctions lists, each fetched from the authority that issues it: the OFAC SDN list from the US Treasury (SDN.CSV plus ALT.CSV for alternate spellings), the EU consolidated financial sanctions list from the European Commission, and the UK Sanctions List from the FCDO. THE UN CONSOLIDATED LIST IS NOT SCREENED -- it carries no licence permitting commercial redistribution, so we do not claim it.… [free in quota, then $0.02/call]

Input parameters:

- `country` (string): Optional ISO 3166-1 alpha-2 country code or country name (e.g. 'IR', 'Iran').…
- `name` (string, required): Full name of the person or entity to screen, e.g. 'Kim Jong-un' or 'ACME…
- `type` (string): Optional entity type hint. 'person' for individuals, 'entity' for…

### `map_trade_restriction` (~264 tokens)

Free cross-border trade screening of the DESTINATION and the PARTIES. IT DOES NOT CLASSIFY THE PRODUCT: the product argument is recorded and echoed back, never checked against any export-control list, so a controlled item to an unrestricted destination returns no findings and reason_code 'partial' -- never 'clear'. This is not an export-control clearance; classify the item (HS/ECCN) against BIS/EU/UK controls yourself. Given a product and… [free in quota, then $0.02/call]

Input parameters:

- `destination_country` (string, required): ISO 3166-1 alpha-2 code for the importing country (e.g. 'IR', 'CA', 'DE').…
- `hs_code` (string): Optional Harmonized System code (e.g. '8471.30' for laptops). If provided,…
- `origin_country` (string): Optional ISO 3166-1 alpha-2 code for the exporting country (e.g. 'US', 'DE').…
- `parties` (array): Optional list of party names to screen (exporter, importer, freight forwarder,…
- `product` (string, required): Product name or description, e.g. 'laptop computers', 'crude oil', 'medical…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-hatchloop-compliance-check/mcp-compliance-check#diagnostics

## Score history

- 2026-09-22: 82
- 2026-09-21: 82
- 2026-09-20: 81
- 2026-09-19: 81
- 2026-09-18: 80
- 2026-09-17: 80
- 2026-09-16: 79
- 2026-09-15: 79
- 2026-09-14: 78
- 2026-09-13: 78
- 2026-09-12: 78
- 2026-09-11: 77
- 2026-09-10: 74
- 2026-09-09: 76
- 2026-09-08: 76
- 2026-09-07: 72
- 2026-09-06: 72
- 2026-09-05: 72
- 2026-09-04: 71
- 2026-09-03: 71
- 2026-09-02: 70
- 2026-09-01: 70

## Common questions

### What is the Compliance Check MCP server?

Compliance Check is an MCP server listed in the public MCP registry as dev.hatchloop/compliance-check. Preview a TCPA/GDPR/CASL/10DLC gate result before spending a paid send. No key needed. This page covers its hosted endpoint (https://hatchloop.dev/mcp/compliance-check).

### Is the Compliance Check MCP server safe to use?

Compliance Check scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Compliance Check MCP server expose?

Compliance Check exposes 8 tools: get_status, get_outcome, preview_cost, self_test, check_compliance, and 3 more. Their descriptions and schemas cost roughly 1,155 tokens of context every time the server is loaded.

### Does the Compliance Check MCP server require authentication?

No. We connected to Compliance Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Compliance Check MCP server still maintained?

Compliance Check is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://hatchloop.dev/mcp/compliance-check
- Repository: https://github.com/basilalshukaili/agentbroker
- Website: https://hatchloop.dev/agent-broker/
- Changelog RSS feed: https://verifymcp.io/servers/dev-hatchloop-compliance-check/mcp-compliance-check.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-hatchloop-compliance-check/mcp-compliance-check.json
- HTML version of this page: https://verifymcp.io/servers/dev-hatchloop-compliance-check/mcp-compliance-check