Compliance Registry
REMOTE · COMPLIANCEREGISTRY.NET
First A2A registry where AI agents discover & transact with compliance firms - audits, permits.
Available components
Last scanned (5 hours ago)
Scores higher than 13% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 421. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 10 Oct 26 −50
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: fail → pass ▲ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 5 Oct 26 0
- Stability: 0.97 → pass security
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 75
- Stability: pass → 0.93 functional
- 2 Oct 26 0
- Stability: 0.97 → pass security
- 1 Oct 26 0
- Injection markers: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.97 ▲ functional
- 30 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 29 Sept 26 0
- Endpoint reachability: not serving MCP → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://complianceregistry.net/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=complianceregistry.net | CN=YE1,O=Let's Encrypt,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6cbbc623c15fbf2784d38d914eaf76b66f1 |
| SANs: *.complianceregistry.net, complianceregistry.net | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of complianceregistry.net. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| complianceregistry.net. | present | 2371 | 13 | Verified |
| complianceregistry.net. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 421 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://complianceregistry.net/mcp/ | HTTP error | 421 | |
| http (plaintext) | http://complianceregistry.net/mcp/ | HTTPS enforced | 301 | https://complianceregistry.net/mcp/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
claim_listing ~107
Record a firm's intent to claim its directory listing. Pre-OAuth, TESSA logs the claim and a representative reaches out via email within one business day to verify the claimant and switch the listing's verification status to 'claimed'. Full self-service OAuth-2.1 claim flow lands in a follow-up plan.
| Name | Type | Req | Description |
|---|---|---|---|
| claim_email | string | yes | – |
| claimant_name | – | – | – |
| claimant_role | – | – | – |
| firm_slug | string | yes | – |
No output schema declared.
No examples provided.
find_compliance_firm ~124
Search the Compliance Registry for vetted compliance and regulatory firms. sub_vertical: 'environmental_compliance' | 'accessibility' (or free-text keyword) region: city or state name (case-insensitive contains) capability: keyword to match against firm descriptions and service names (e.g., 'phase i esa', 'wcag', 'permits', 'inspections') limit: max results
| Name | Type | Req | Description |
|---|---|---|---|
| capability | – | – | – |
| limit | integer | – | – |
| region | – | – | – |
| sub_vertical | – | – | – |
No output schema declared.
No examples provided.
get_firm_profile ~66
Full dossier for a single firm in the Compliance Registry: description, headquarters, founded year, employee band, services, locations, sub-vertical, taxonomy, and directory meta (publisher, claim URL, takedown URL).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_wcag_audit ~83
Structured offering for TESSA's WCAG 2.2 AA Accessibility Audit: scope, deliverables, timeline, pricing bands (hourly + engagement range), paired service-type slugs, and TESSA's profile URL in the Compliance Registry. Use when a buyer agent wants accessibility audit details in structured form.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_introduction ~116
Request a warm introduction to a Compliance Registry firm. target_firm_slug is required (this tool routes leads to listed firms, not to TESSA directly). TESSA logs the lead and forwards a warm intro email to the firm with TESSA Cc'd. No calendar booking.
| Name | Type | Req | Description |
|---|---|---|---|
| project_brief | – | – | – |
| prospect_email | string | yes | – |
| prospect_name | – | – | – |
| prospect_org | – | – | – |
| requested_window | – | – | – |
| target_firm_slug | string | yes | – |
No output schema declared.
No examples provided.
request_quote ~150
Request a quote from a Compliance Registry firm. firm_slug: directory slug for the target firm prospect_email: caller's email for the firm's reply scope_summary: one-paragraph description of the work budget_band: 'under_5k' | '5k_25k' | '25k_100k' | '100k_plus' | 'open' — or any free-text dollar figure
| Name | Type | Req | Description |
|---|---|---|---|
| budget_band | – | – | – |
| firm_slug | string | yes | – |
| prospect_email | string | yes | – |
| prospect_name | – | – | – |
| prospect_org | – | – | – |
| requested_window | – | – | – |
| scope_summary | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Compliance Registry MCP server?
Compliance Registry is a hosted endpoint at https://complianceregistry.net/mcp/, 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.
remote · complianceregistry.net
claude mcp add --transport http net-complianceregistry-mcp-server 'https://complianceregistry.net/mcp/'
What is the Compliance Registry MCP server?
Compliance Registry is an MCP server listed in the public MCP registry as net.complianceregistry/mcp-server. First A2A registry where AI agents discover & transact with compliance firms - audits, permits. This page covers its hosted endpoint (https://complianceregistry.net/mcp/).
Is the Compliance Registry MCP server safe to use?
Compliance Registry scores 26 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 Registry MCP server expose?
Compliance Registry exposes 6 tools: find_compliance_firm, get_wcag_audit, get_firm_profile, request_introduction, claim_listing, request_quote. Their descriptions and schemas cost roughly 646 tokens of context every time the server is loaded.
Does the Compliance Registry MCP server require authentication?
Its publisher declares no required credentials for Compliance Registry. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Compliance Registry MCP server still maintained?
Compliance Registry is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.