ICANN registrar accreditation status

io.github.joelp22-maker由 GitHub 账号 joelp22-maker 发布v1.0.0更新于 Nov 2, 2026

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

发布方自己的服务：status.live national parks

已验证Streamable HTTP可网页运行网页搜索与抓取知识与记忆

服务详情

标识符: io.github.joelp22-maker/referencesource-registrars
传输: Streamable HTTP
运行时: Web executable
信任: Verified
发布于: Sep 21, 2026

安全提示

MCP 服务会接收对话中的工具调用请求，并可能执行外部操作。启用前请先了解该服务能做什么，并只授予它所需的权限。

注册中心已验证此条目所属的 GitHub 账号 joelp22-maker。这并不表明该账号就是产品方。

SourceWeft 的检查只涵盖条目是否完整、端点是否响应；不审查服务器的代码，也不审查其工具的行为。

在 README 中添加徽章

向读者展示该 MCP 服务已收录于 SourceWeft，徽章链接到本页。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.joelp22-maker%2Freferencesource-registrars.svg)](https://sourceweft.com/mcp/io.github.joelp22-maker%2Freferencesource-registrars?utm_source=readme&utm_medium=badge)

概览

AI 生成的概览

查询 ICANN 认证域名注册商及其执法行动，每条结果都附带来源页面和原文引用。

可以做什么: 按注册商名称或 IANA ID 查找注册商，查看其认证状态与 ICANN 执法行动
按 IANA 注册商 ID 获取该注册商的全部记录，包括 RDAP 基础地址及违约、暂停或终止通知
按行动类型或日期筛选，按时间倒序列出合同合规通知
核对关于注册商状态、名称或执法日期的说法是否与已存记录一致，并返回判定结果与来源引用
适用场景: 需要确认某域名注册商是否仍获 ICANN 认证、ICANN 是否对其采取过行动，或核实助手给出的注册商相关说法是否有来源支持时使用。
运行要求: 远程 streamable-HTTP 端点；未声明需要账号、API 密钥或环境变量。README 另提到可选的本地 npm 包（Node 18+），用于把 stdio 客户端桥接到同一端点。

安装前请注意

仅做只读查询，但判定结果只反映登记册来源所述内容，并非现实中的事实；未找到表示该数据集中没有此记录，而非该说法为假。请求会发送到第三方服务器，该服务器保留常规请求日志。

安装

在 SourceWeft 中

打开控制台中的 ICANN registrar accreditation status，将其添加到工作区。
为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.joelp22-maker%2Freferencesource-registrars/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "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

tool	what it does
`list_datasets`	every dataset with record counts and descriptions
`search_records`	search within a dataset; each hit returns the value plus its source URL and verbatim source quote
`get_record`	one record by id, full provenance included
`verify_quote`	give 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:

verdict	what it means
`matches_record`	the claim equals the stored value; the match type is named (exact, case-insensitive, normalised)
`matches_quote`	not a stored value, but it does appear in the record's source quote
`differs`	the record holds a different value — both are returned, with the source
`not_found`	no 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"]    }  }}

{  "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

Site: https://referencesource.org — canonical, re-verified on a schedule
Bulk data: https://github.com/joelp22-maker/referencesource-data
Archived snapshot with a DOI: 10.5281/zenodo.22115966
Hugging Face: https://huggingface.co/datasets/referencesource

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.

来源：README.md，提交 e0de5e7

工具

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.

输入参数query必填status

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.

输入参数iana_id必填

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.

输入参数limitsinceaction

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.

输入参数fieldiana_id必填claimed_value必填