Local MCP capabilities provider for Expo
Compliance Check is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Preview a TCPA/GDPR/CASL/10DLC gate result before spending a paid send. No key needed.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http compliance-check-mcp https://hatchloop.dev/mcp/compliance-check
# 2 — ask your agent for something these tools do
# get_status, get_outcome, preview_cost and 5 more
Compliance Check costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http compliance-check-mcp https://hatchloop.dev/mcp/compliance-checkReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Query the current state of any in-flight async operation by operation_id. [free, no key]
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operation_id | string | yes | — |
Retrieve the final OutcomeReceipt for a completed operation. [free, no key]
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operation_id | string | yes | — |
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]
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operation | string | yes | — |
| params | object | yes | The same request body you would pass to the operation |
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]
No parameter schema on file.
Free, instant pre-flight for the compliance gate: runs the SAME TCPA/GDPR/CASL/CAN-SPAM/10DLC checks as send_message and call_business, in preview mode -- nothing is sent, nothing changes. Tells you whether a send would be permitted before you pay, and if not, names the exact rule and how to fix it. De-risks a paid send the way check_booking_link de-risks a paid booking. [free, no key]
| Parameter | Type | Required | Notes |
|---|---|---|---|
| recipient_id | string | yes | Phone in E.164 (e.g. '+14045550100') or email address the message would go to. |
| content | string | yes | The actual message body you intend to send. The gate classifies the real text,… |
| channel | string | no | Delivery channel. Omit to auto-infer sms/email from recipient_id; set 'voice'… |
| message_type | string | no | One of transactional, marketing, reminder, follow_up, notification (any case).… |
| country_code | string | no | ISO 3166-1 alpha-2 (e.g. 'US', 'DE', 'CA'). Auto-inferred from phone if… |
| state_code | string | no | US state code (e.g. 'CA') for state-specific rules. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Legal company name to look up, e.g. Apple Inc or Volkswagen AG. |
| country | string | no | Optional ISO 3166-1 alpha-2 country filter (e.g. US, DE, GB). Narrows GLEIF… |
| lei | string | no | Optional 20-character Legal Entity Identifier for a direct, precise lookup. |
Free screening of a name/entity (Latin or Arabic script) against sanctions lists: OFAC SDN (US Treasury), EU consolidated list (European Commission), UK Sanctions List (FCDO). THE UN CONSOLIDATED LIST IS NOT SCREENED -- no licence permits redistribution. Never fabricates a match or clear: check lists_screened; reason_code 'partial_screening' (never 'clear') if any source failed. [free, no key]
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Name of the person or entity to screen, in Latin or Arabic script, e.g. 'Kim… |
| country | string | no | Optional ISO 3166-1 alpha-2 country code or country name (e.g. 'IR', 'Iran').… |
| type | string | no | Optional entity type hint. 'person' for individuals, 'entity' for… |
Free cross-border screening of destination and parties: DOES NOT CLASSIFY THE PRODUCT: echoed back, never checked against export-control lists, so a controlled item to an unrestricted destination returns 'partial', never 'clear'. Not an export-control clearance -- classify HS/ECCN yourself. Never fabricates a tariff rate, a clear, or a restricted status. [free, no key]
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | yes | Product name or description, e.g. 'laptop computers', 'crude oil', 'medical… |
| hs_code | string | no | Optional Harmonized System code (e.g. '8471.30' for laptops). If provided,… |
| origin_country | string | no | Optional ISO 3166-1 alpha-2 code for the exporting country (e.g. 'US', 'DE').… |
| destination_country | string | yes | ISO 3166-1 alpha-2 code for the importing country (e.g. 'IR', 'CA', 'DE').… |
| parties | array | no | Optional list of party names to screen (exporter, importer, freight forwarder,… |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Compliance Check or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_status | no tags | |
| get_outcome | no tags | |
| preview_cost | no tags | |
| self_test | no tags | |
| check_compliance | no tags | |
| verify_company_record | no tags | |
| screen_sanctions | no tags | |
| map_trade_restriction | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.2.13.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Compliance Check can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.