ICANN registrar accreditation status
REMOTE · REFERENCESOURCE.ORG · SCANNED SEP 21
Is a domain registrar still ICANN-accredited, and has ICANN acted against it? 4,500+ registrars.
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 778 tokens (~194/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: 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 ICANN registrar accreditation status MCP server?
ICANN registrar accreditation status is a hosted endpoint at https://referencesource.org/mcp/registrars, 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 · referencesource.org
claude mcp add --transport http joelp22-maker-referencesource-registrars 'https://referencesource.org/mcp/registrars'
{
"mcpServers": {
"joelp22-maker-referencesource-registrars": {
"url": "https://referencesource.org/mcp/registrars"
}
}
} {
"servers": {
"joelp22-maker-referencesource-registrars": {
"type": "http",
"url": "https://referencesource.org/mcp/registrars"
}
}
} [mcp_servers.joelp22-maker-referencesource-registrars] url = "https://referencesource.org/mcp/registrars"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"joelp22-maker-referencesource-registrars": {
"type": "remote",
"url": "https://referencesource.org/mcp/registrars",
"enabled": true
}
}
} openclaw mcp add joelp22-maker-referencesource-registrars --url 'https://referencesource.org/mcp/registrars' --transport streamable-http
mcp_servers:
joelp22-maker-referencesource-registrars:
url: "https://referencesource.org/mcp/registrars" {
"McpServers": {
"joelp22-maker-referencesource-registrars": {
"Transport": "http",
"Url": "https://referencesource.org/mcp/registrars"
}
}
} assistant mcp add joelp22-maker-referencesource-registrars -t streamable-http -u 'https://referencesource.org/mcp/registrars'
{
"mcpServers": {
"joelp22-maker-referencesource-registrars": {
"type": "http",
"url": "https://referencesource.org/mcp/registrars"
}
}
} 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.
- 21 Sept 26 71
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 21 Sept 2026 · Probed https://referencesource.org/mcp/registrars
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=referencesource.org | CN=WE1,O=Google Trust Services,C=US | 5 Aug 2026 | 3 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 9f260b3a10521b060ef7a85ccbf0f716 |
| SANs: referencesource.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of referencesource.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| referencesource.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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://referencesource.org/mcp/registrars | Verified | 200 | |
| http (plaintext) | http://referencesource.org/mcp/registrars | HTTPS enforced | 301 | https://referencesource.org/mcp/registrars |
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 →
get_registrar Get a registrar's status and enforcement history by IANA ID ~118
Everything this register holds for one IANA registrar ID: accreditation status, RDAP base URL, and any ICANN breach, suspension or termination notice with the date and the notice PDF — each with its source page and a verbatim quote. Returns a LIST: ten IDs today carry two records because ICANN and IANA spell the registrar's name differently, and both are returned rather than one being chosen.
| Name | Type | Req | Description |
|---|---|---|---|
| iana_id | string | yes | The IANA registrar ID, e.g. "146" (GoDaddy) or "13". |
| Name | Type | Req | Description |
|---|---|---|---|
| iana_id | string | yes | – |
| records_found | integer | yes | – |
| register | object | – | – |
| registrars | array | yes | – |
No examples provided.
list_enforcement_actions List ICANN enforcement notices ~164
Which registrars has ICANN acted against? Lists the Contractual Compliance notices in this register — breach, suspension and termination — newest first, with the registrar, the date as ICANN prints it, the notice PDF and a verbatim quote of the notice line. Filter by action type or by date to see recent enforcement.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Optional: only this kind of notice. |
| limit | integer | – | How many to return, 1–20. Default 20. |
| since | string | – | Optional ISO date, e.g. "2024-01-01". Only notices dated on or after it. ICANN prints dates in long form ("20 November 2017"); this filter compares an ISO form computed from that string here. |
| Name | Type | Req | Description |
|---|---|---|---|
| notices | array | yes | – |
| notices_matched | integer | yes | – |
| notices_returned | integer | – | – |
| register | object | – | – |
No examples provided.
resolve_registrar Find a registrar by name or IANA ID ~149
Which registrar is this? Search ICANN's accredited-registrar register by registrar name (or part of one, e.g. "GoDaddy", "Tucows", "namecheap") or by IANA registrar ID. Returns the matching registrars with their accreditation status and any ICANN enforcement action, each with the page and verbatim quote it was read from. Use this first when you have a name; use get_registrar when you already have the IANA ID.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Registrar name or part of one, or an IANA registrar ID. Case-insensitive substring match. |
| status | string | – | Optional: return only registrars with this accreditation status. |
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| register | object | – | – |
| registrars | array | yes | – |
| registrars_matched | integer | yes | – |
| registrars_returned | integer | – | – |
No examples provided.
verify_quote Check a claimed registrar fact against the register ~165
Is this right? Check a claim about a registrar — its accreditation status, its name, an enforcement date — against the register instead of trusting it. Says whether the claim matches a stored value, appears only in the verbatim source quote, or differs (and then what the register says instead), and returns the source page and quote so the claim can be traced upstream.
| Name | Type | Req | Description |
|---|---|---|---|
| claimed_value | string | yes | The value to check, exactly as claimed, e.g. "Terminated" or "2026-10-29". |
| field | string | – | Which field the claim is about, if you know it. Without it, every stored field of the record is checked. |
| iana_id | string | yes | The IANA registrar ID of the registrar the claim is about. |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | string | yes | – |
| claimed_value | string | yes | – |
| in_source_quote | boolean | – | – |
| match | object | – | – |
| quote_source | string | – | – |
| record | object | – | – |
| stored_values | object | – | – |
| verdict | string | yes | matches_record: the claim equals a stored value (match.match_type says how exactly). matches_quote: it appears in the verbatim source quote but is not a stored value. differs: the record was found an… |
No examples provided.
What is the ICANN registrar accreditation status MCP server?
ICANN registrar accreditation status is an MCP server listed in the public MCP registry as io.github.joelp22-maker/referencesource-registrars. Is a domain registrar still ICANN-accredited, and has ICANN acted against it? 4,500+ registrars. This page covers its hosted endpoint (https://referencesource.org/mcp/registrars).
Is the ICANN registrar accreditation status MCP server safe to use?
ICANN registrar accreditation status scores 71 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 ICANN registrar accreditation status MCP server expose?
ICANN registrar accreditation status exposes 4 tools: resolve_registrar, get_registrar, list_enforcement_actions, verify_quote. Their descriptions and schemas cost roughly 596 tokens of context every time the server is loaded.
Does the ICANN registrar accreditation status MCP server require authentication?
No. We connected to ICANN registrar accreditation status without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ICANN registrar accreditation status MCP server still maintained?
ICANN registrar accreditation status is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.