Compliance Registry
REMOTE · COMPLIANCEREGISTRY.NET · SCANNED AUG 3
First A2A registry where AI agents discover & transact with compliance firms - audits, permits.
Available components
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 →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 646 tokens (~107/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · complianceregistry.net
claude mcp add --transport http net-complianceregistry-mcp-server https://complianceregistry.net/mcp/
[mcp_servers.net-complianceregistry-mcp-server] url = "https://complianceregistry.net/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"net-complianceregistry-mcp-server": {
"type": "remote",
"url": "https://complianceregistry.net/mcp/",
"enabled": true
}
}
} openclaw mcp add net-complianceregistry-mcp-server --url https://complianceregistry.net/mcp/ --transport streamable-http
mcp_servers:
net-complianceregistry-mcp-server:
url: "https://complianceregistry.net/mcp/" {
"mcpServers": {
"net-complianceregistry-mcp-server": {
"type": "http",
"url": "https://complianceregistry.net/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +23
- 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
- Schema quality: unverified → fail ▼ functional
- Schema quality: unverified → good ▲ functional
- Schema quality: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: fail → 0.23 functional
- New tool “request_quote” functional
- New tool “request_introduction” functional
- New tool “get_wcag_audit” functional
- New tool “get_firm_profile” functional
- New tool “find_compliance_firm” functional
- New tool “claim_listing” functional
- 31 Jul 26 −20
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +28
- 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
- Schema quality: unverified → fail ▼ functional
- Schema quality: unverified → good ▲ functional
- Schema quality: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: fail → 0.07 functional
- New tool “request_quote” functional
- New tool “request_introduction” functional
- New tool “get_wcag_audit” functional
- New tool “get_firm_profile” functional
- New tool “find_compliance_firm” functional
- New tool “claim_listing” functional
- 27 Jul 26 −27
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 57
First indexed and scored.
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 3 Aug 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 | 22 Jun 2026 | 20 Sept 2026 | ECDSA 256 | ECDSA-SHA384 | 5e8b2acd497e635ba9204a3332f2cda4574 |
| 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 |
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 No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://complianceregistry.net/mcp/ | Verified | 200 | |
| 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.
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.