# ICANN registrar accreditation status (remote · referencesource.org)

Is a domain registrar still ICANN-accredited, and has ICANN acted against it? 4,500+ registrars.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `referencesource.org`: 71/100 (this document), [markdown](https://verifymcp.io/servers/joelp22-maker-referencesource-registrars/mcp-registrars.md), [page](https://verifymcp.io/servers/joelp22-maker-referencesource-registrars/mcp-registrars)

## Channel facts

- Endpoint: `https://referencesource.org/mcp/registrars`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http joelp22-maker-referencesource-registrars 'https://referencesource.org/mcp/registrars'
```

### Cursor

```json
{
  "mcpServers": {
    "joelp22-maker-referencesource-registrars": {
      "url": "https://referencesource.org/mcp/registrars"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "joelp22-maker-referencesource-registrars": {
      "type": "http",
      "url": "https://referencesource.org/mcp/registrars"
    }
  }
}
```

### Codex

```toml
[mcp_servers.joelp22-maker-referencesource-registrars]
url = "https://referencesource.org/mcp/registrars"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "joelp22-maker-referencesource-registrars": {
      "type": "remote",
      "url": "https://referencesource.org/mcp/registrars",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add joelp22-maker-referencesource-registrars --url 'https://referencesource.org/mcp/registrars' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  joelp22-maker-referencesource-registrars:
    url: "https://referencesource.org/mcp/registrars"
```

### Netclaw

```json
{
  "McpServers": {
    "joelp22-maker-referencesource-registrars": {
      "Transport": "http",
      "Url": "https://referencesource.org/mcp/registrars"
    }
  }
}
```

### Vellum

```bash
assistant mcp add joelp22-maker-referencesource-registrars -t streamable-http -u 'https://referencesource.org/mcp/registrars'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 71)

First indexed and scored.

## MCP tools (4)

### `resolve_registrar` (~149 tokens)

Find a registrar by name or IANA ID

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.

Input parameters:

- `query` (string, required): 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.

Output parameters:

- `query` (string)
- `register` (object)
- `registrars` (array)
- `registrars_matched` (integer)
- `registrars_returned` (integer)

### `get_registrar` (~118 tokens)

Get a registrar's status and enforcement history by IANA ID

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.

Input parameters:

- `iana_id` (string, required): The IANA registrar ID, e.g. "146" (GoDaddy) or "13".

Output parameters:

- `iana_id` (string)
- `records_found` (integer)
- `register` (object)
- `registrars` (array)

### `list_enforcement_actions` (~164 tokens)

List ICANN enforcement notices

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.

Input parameters:

- `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.

Output parameters:

- `notices` (array)
- `notices_matched` (integer)
- `notices_returned` (integer)
- `register` (object)

### `verify_quote` (~165 tokens)

Check a claimed registrar fact against the register

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.

Input parameters:

- `claimed_value` (string, required): 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, required): The IANA registrar ID of the registrar the claim is about.

Output parameters:

- `attestation` (string)
- `claimed_value` (string)
- `in_source_quote` (boolean)
- `match` (object)
- `quote_source` (string)
- `record` (object)
- `stored_values` (object)
- `verdict` (string): 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…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/joelp22-maker-referencesource-registrars/mcp-registrars#diagnostics

## Score history

- 2026-09-21: 71

## Common questions

### 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.

## Links

- Remote endpoint: https://referencesource.org/mcp/registrars
- Repository: https://github.com/joelp22-maker/referencesource-mcp
- Website: https://referencesource.org/icann-registrar-accreditation-status
- Changelog RSS feed: https://verifymcp.io/servers/joelp22-maker-referencesource-registrars/mcp-registrars.xml
- Changelog JSON feed: https://verifymcp.io/servers/joelp22-maker-referencesource-registrars/mcp-registrars.json
- HTML version of this page: https://verifymcp.io/servers/joelp22-maker-referencesource-registrars/mcp-registrars