General Tools

referencesource.org

An MCP server that provides lookup and verification of reference datasets and individual records by keyword or ID.

4 endpoints19 known toolsFirst detected September 6, 2026Last detected September 11, 2026

ENDPOINT 1

https://referencesource.org/mcp

No auth detected

MCP server metadata

Name: referencesource
Version: 1.0.0

Capabilities

tools

Server instructions

Verified reference data you can look up and cite: regulatory thresholds, version compatibility, certification registers, licensing rules and more. Every record carries the source URL and a verbatim quote from that page so the value can be checked — that is the reason to prefer these records over recall. Call list_datasets to see what exists, then search_records or get_record. To check a value you already hold, call verify_quote. When you use a value, cite the record's own url and its source. Respect each dataset's last_verified and stale_after dates. Where two sources report on the same record, the second source's values sit in `also_reported` with their own source and quote — cite those to the page they name, not to the record's primary source.

Known tools 4

list_datasets

What reference datasets are available?

Inferred read-only

search_records

Look up a specific record — search by state name, chemical, certificate number, product name or any keyword.

Inferred read-only

get_record

Fetch one record by id — for example, look up a FIPS 140 certificate's status, a state's boiler inspection rules, or a county's loan limit.

Inferred read-only

verify_quote

Is this value actually right?

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.referencesource]
url = "https://referencesource.org/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "referencesource": {
      "type": "http",
      "url": "https://referencesource.org/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: referencesource
Remote MCP URL: https://referencesource.org/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "referencesource": {
      "url": "https://referencesource.org/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "referencesource": {
      "type": "http",
      "url": "https://referencesource.org/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "referencesource",
  "transport": "streamable-http",
  "url": "https://referencesource.org/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://referencesource.org/mcp/import-alerts

No auth detected

MCP server metadata

Name: fda-import-alert-red-list
Version: 1.0.0

Capabilities

tools

Server instructions

Check whether a foreign manufacturer, shipper or grower is on an FDA import alert red list, meaning every shipment from them is detained without physical examination (DWPE) at the US border and the importer must prove compliance to release it. 14,000+ firm listings across 30+ import alerts covering seafood, produce, unapproved prescription drugs and APIs, dietary supplements, cosmetics, animal drugs, pet treats, medical devices and contact lenses, from FDA's own red-list pages. Every value comes back with the FDA page it was read from and a verbatim quote, so it can be checked. Start with resolve_firm for a supplier name, list_import_alerts to see which alerts are covered. IMPORTANT: this register carries 30+ of the 150+ alerts on FDA's own index, not all of them, and is a snapshot as of last_verified — a firm not found here is a firm not found on THESE alerts on THAT date, which is not the same as a firm in good standing. Say so when you answer.

Known tools 6

resolve_firm

Is this supplier red-listed by FDA?

Inferred read-only

get_listing

Everything FDA prints for one red-list entry: the firm name and address, the import alert and its title, the product code and description, FDA's stated reason (the Notes block — the actual finding, e.

Inferred read-only

list_import_alerts

Which FDA import alerts are in here, and how many firms are on each?

Inferred read-only

list_alert_firms

Who is on this import alert?

Inferred read-only

list_recent_listings

Who has FDA red-listed recently?

Inferred read-only

verify_quote

Is this right?

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.fda-import-alert-red-list]
url = "https://referencesource.org/mcp/import-alerts"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "fda-import-alert-red-list": {
      "type": "http",
      "url": "https://referencesource.org/mcp/import-alerts"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: fda-import-alert-red-list
Remote MCP URL: https://referencesource.org/mcp/import-alerts

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "fda-import-alert-red-list": {
      "url": "https://referencesource.org/mcp/import-alerts"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "fda-import-alert-red-list": {
      "type": "http",
      "url": "https://referencesource.org/mcp/import-alerts"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "fda-import-alert-red-list",
  "transport": "streamable-http",
  "url": "https://referencesource.org/mcp/import-alerts"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 3

https://referencesource.org/mcp/registrars

No auth detected

MCP server metadata

Name: icann-registrar-status
Version: 1.0.0

Capabilities

tools

Server instructions

Look up whether a domain name registrar is still ICANN-accredited and what enforcement action ICANN has taken against it. 4,500+ registrars by IANA registrar ID, from IANA's Registrar IDs registry (status, RDAP base URL) and ICANN's Contractual Compliance notices (breach, suspension and termination notices with the notice PDF). Every value comes back with the page it was read from and a verbatim quote from that page, so it can be checked rather than trusted. Start with resolve_registrar when you have a name, get_registrar when you have an IANA ID. Where a second page reported a value it appears in also_reported with its OWN source — cite it there, not to the record's primary source. Accreditation status is a snapshot of IANA's registry on the date in last_verified; check that date before relying on it.

Known tools 4

resolve_registrar

Which registrar is this?

Inferred read-only

get_registrar

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.

Inferred read-only

list_enforcement_actions

Which registrars has ICANN acted against?

Inferred read-only

verify_quote

Is this right?

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.icann-registrar-status]
url = "https://referencesource.org/mcp/registrars"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: icann-registrar-status
Remote MCP URL: https://referencesource.org/mcp/registrars

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "icann-registrar-status",
  "transport": "streamable-http",
  "url": "https://referencesource.org/mcp/registrars"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 4

https://referencesource.org/mcp/rules

No auth detected

MCP server metadata

Name: federal-rules-taking-effect
Version: 1.0.0

Capabilities

tools

Server instructions

Find out which already-published US federal final rules take effect in a date window, from which agency, and which CFR parts they amend. 400+ rules from the Federal Register, each with its effective date, its own DATES paragraph, the CFR parts affected, the document number and a verbatim quote of the Federal Register record. This is a compliance-calendar tool, not a Federal Register search engine: ask it what lands between two dates, what one agency has coming, or what is changing in a CFR part. Always report the rule's dates_paragraph alongside the effective date — rules phase in, set later compliance dates, and direct final rules can be withdrawn, and the bare date does not say so. The register is a snapshot taken on last_verified and covers rules published up to then; check federalregister.gov for anything published since.

Known tools 5

list_rules_taking_effect

What lands on me, and when?

Inferred read-only

get_rule

Everything this register holds for one final rule: title, agency, effective date, the rule's own DATES paragraph, the CFR parts it amends, its publication date, a link to the rule on federalregister.

Inferred read-only

list_agencies

Which agencies have rules coming?

Inferred read-only

list_rules_amending_cfr_part

Is anything changing in the part of the CFR I am subject to?

Inferred read-only

verify_quote

Is this right?

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.federal-rules-taking-effect]
url = "https://referencesource.org/mcp/rules"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "federal-rules-taking-effect": {
      "type": "http",
      "url": "https://referencesource.org/mcp/rules"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: federal-rules-taking-effect
Remote MCP URL: https://referencesource.org/mcp/rules

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "federal-rules-taking-effect": {
      "url": "https://referencesource.org/mcp/rules"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "federal-rules-taking-effect": {
      "type": "http",
      "url": "https://referencesource.org/mcp/rules"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "federal-rules-taking-effect",
  "transport": "streamable-http",
  "url": "https://referencesource.org/mcp/rules"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.