Skip to content

ICANN registrar accreditation status

by joelp22-maker · remote · no sign-in to list tools · v1.0.0 · published by GitHub user joelp22-maker

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

Changes · 1
CompareRegistry entry

4 tools: 1 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http referencesource-registrars https://referencesource.org/mcp/registrars

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 1Claude Code: ask
  • verify_quoteIs this right?No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check a claimed registrar fact against the register
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 3Claude Code: allow
  • get_registrarEverything 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 P…No findings

    Why it is in this group

    • The name "get_registrar" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get a registrar's status and enforcement history by IANA ID
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_enforcement_actionsWhich registrars has ICANN acted against?No findings

    Why it is in this group

    • The name "list_enforcement_actions" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List ICANN enforcement notices
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • resolve_registrarWhich registrar is this?No findings

    Why it is in this group

    • The name "resolve_registrar" says "resolve": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find a registrar by name or IANA ID
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http referencesource-registrars https://referencesource.org/mcp/registrars

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__referencesource-registrars__resolve_registrar",
      "mcp__referencesource-registrars__get_registrar",
      "mcp__referencesource-registrars__list_enforcement_actions"
    ],
    "ask": [
      "mcp__referencesource-registrars__verify_quote"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as referencesource-registrars. Review it before you use it.