ICANN registrar accreditation status

io.github.joelp22-makerPublished by GitHub account joelp22-makerv1.0.0Updated Nov 2, 2026

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

The publisher's own server: status.live national parks

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

Looks up ICANN-accredited domain registrars and enforcement actions, returning each answer with its source page and a verbatim quote.

What you can do
  • Resolve a registrar by name or IANA ID and see its accreditation status and any ICANN enforcement action
  • Fetch everything held for one IANA registrar ID, including RDAP base URL and breach, suspension or termination notices
  • List contractual compliance notices newest first, filtered by action type or date
  • Check a claim about a registrar's status, name or enforcement date against the stored records and get a verdict with the source quote
When to use it
Useful when you need to confirm whether a domain registrar is still ICANN-accredited, whether ICANN has taken action against it, or whether a registrar-related claim an assistant produced is actually supported by a source.
Requirements
Remote streamable-HTTP endpoint; no account, API key or environment variable is declared. The README also describes an optional local npm package (Node 18+) that bridges stdio clients to the same endpoint.
Before you install
Read-only lookups, but verdicts describe what the register's source states, not ground truth in the world; a not-found result means the item is not in the dataset, not that it is false. Requests reach a third-party server that keeps standard request logs.

Installation

In SourceWeft

  1. Open ICANN registrar accreditation status in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.joelp22-maker%2Freferencesource-registrars/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "icann-registrar-accreditation-status": {
      "type": "http",
      "url": "https://referencesource.org/mcp/registrars"
    }
  }
}

README

referencesource-mcp

[referencesource.org MCP connector]

MCP server for referencesource.org — small, verified reference datasets where every record carries its source URL and a verbatim quote from that page, so any value an assistant gives you can be checked, not just believed.

285 datasets, 110,000+ records: regulatory thresholds and deadlines, version compatibility, standards supersessions, certification registers, inspection requirements, and more. Each dataset states its coverage and its last-verified date.

Tools

toolwhat it does
list_datasetsevery dataset with record counts and descriptions
search_recordssearch within a dataset; each hit returns the value plus its source URL and verbatim source quote
get_recordone record by id, full provenance included
verify_quotegive it a dataset slug and a value you already hold (record id and field optional) — it checks that claim against our published records and says whether it matches

verify_quote is the unusual one: assistants invent plausible-but-wrong values roughly 19% of the time in our own measurements, and this is the check. Four verdicts come back:

verdictwhat it means
matches_recordthe claim equals the stored value; the match type is named (exact, case-insensitive, normalised)
matches_quotenot a stored value, but it does appear in the record's source quote
differsthe record holds a different value — both are returned, with the source
not_foundno record in that dataset carries it

Where a record is found, the answer carries the stored value, the record URL, the source URL and the verbatim quote, so the claim can be traced upstream — plus an attestation saying plainly that the verdict is about what our source states, not about what is true in the world. Asking whether the 2026 conforming loan limit for Autauga County, Alabama is $806,500 returns differs, stored value $832,750, quoting the FHFA row it came from.

Scope, stated so nobody overclaims: these tools search referencesource.org's own published records. They do not fetch arbitrary URLs and cannot check a claim against a page we have not harvested. not_found means "not in this dataset", never "false".

Setup

Claude Desktop — add to claude_desktop_config.json:

json
{  "mcpServers": {    "referencesource": {      "command": "npx",      "args": ["-y", "referencesource-mcp"]    }  }}

Cursor / other stdio MCP clients — same idea: command npx, args ["-y", "referencesource-mcp"].

Clients that support remote servers directly don't need this package at all — point them at the streamable-HTTP endpoint: https://referencesource.org/mcp.

Notes

  • Zero dependencies; Node 18+. The package is a thin stdio→HTTPS bridge to the stateless server at referencesource.org/mcp.
  • No accounts, no keys, no tracking beyond standard server request logs (see referencesource.org/privacy).
  • Data is free to read on the site in HTML, Markdown, and JSON; this package just makes it callable mid-conversation.

MIT licensed.

The data behind it

Every record carries source (the page the value was read from) and source_quote (the verbatim line on that page which states it), so any answer this server returns can be checked against its source. verify_quote runs that check against a value you already hold: it tells you whether our record agrees, and hands back the source and quote either way.

Licence

MIT — see LICENSE. The reference data itself is CC BY 4.0; see the data repository for the full position on the quoted excerpts.

Source: README.md at commit e0de5e7

Tools

4

resolve_registrar

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.

Parametersqueryrequiredstatus

get_registrar

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.

Parametersiana_idrequired

list_enforcement_actions

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.

Parameterslimitsinceaction

verify_quote

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.

Parametersfieldiana_idrequiredclaimed_valuerequired

Version history

1
  1. v1.0.0LatestSep 21, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Status integrations

status.live national parks

live.statusOfficial publisher

Remote MCP server that lets an assistant look up US and Canadian national parks, current alerts and conditions, and nearby campgrounds.

Streamable HTTPWeb executable
Location & Lifestyle3 toolsNov 5, 2026

status.live campgrounds

live.statusOfficial publisher

Remote MCP server that tells an assistant which of about 4,200 US national park and national forest campgrounds are open today, with booking links.

Streamable HTTPWeb executable
Location & Lifestyle3 toolsNov 5, 2026

status.live theme parks

live.statusOfficial publisher

A remote MCP server that lets an assistant look up theme parks and check live ride status, wait times, local time and weather forecasts.

Streamable HTTPWeb executable
Location & Lifestyle2 toolsOct 24, 2026

status.live surf

live.statusOfficial publisher

Remote MCP server that gives an assistant NOAA buoy readings, tides and a 7-day swell forecast for 150+ surf spots.

Streamable HTTPWeb executable
Location & Lifestyle2 toolsOct 24, 2026

status.live

live.statusOfficial publisher

Remote MCP server giving assistants live status for ski resorts, theme parks, national parks, campgrounds and surf spots.

Streamable HTTPWeb executable
Location & Lifestyle17 toolsNov 5, 2026