Compliance Registry
REMOTE · COMPLIANCEREGISTRY.NET · SCANNED SEP 20
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 → Why this is hard to 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 connect, but we couldn't read the tool list to see what that exposes. 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 Usability0
- Instruction-quality not yet verified: the AI judgement didn't run.Unverified
- Nothing to assess: this server exposes no tool/resource definitions to measure a footprint for. See how to fix → Fail
- Nothing to assess: this server has no tools to check for usage examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 30 days we've observed: 6 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 2 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.
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/'
{
"mcpServers": {
"net-complianceregistry-mcp-server": {
"url": "https://complianceregistry.net/mcp/"
}
}
} {
"servers": {
"net-complianceregistry-mcp-server": {
"type": "http",
"url": "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": {
"Transport": "http",
"Url": "https://complianceregistry.net/mcp/"
}
}
} assistant mcp add net-complianceregistry-mcp-server -t streamable-http -u '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.
- 20 Sept 26 +4
- Stability: unverified → fail ▼ security
- Schema quality: fail → unverified ▼ functional
- Schema quality: good → unverified ▼ functional
- Schema quality: pass → unverified ▼ functional
- 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
- 19 Sept 26 −42
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 18 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Sept 26 +42
- Injection markers: unverified → pass ▲ security
- Stability: 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
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 15 Sept 26 −42
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 14 Sept 26 +42
- Injection markers: unverified → pass ▲ security
- Stability: 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
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Server version: 1.29.0 → 1.30.0 functional
- 12 Sept 26 −42
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 11 Sept 26 +42
- Injection markers: unverified → pass ▲ security
- Stability: 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
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ 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 20 Sept 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=YE2,O=Let's Encrypt,C=US | 20 Aug 2026 | 18 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6476bcbf8168296f0d9709d88a501d8bb1b |
| SANs: *.complianceregistry.net, complianceregistry.net | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 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 |
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/ | 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. 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 →
No tool schema has been captured from this endpoint yet.
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 38 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.
Does the Compliance Registry MCP server require authentication?
No. We connected to Compliance Registry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.