Verified reference data; each record carries its source URL and quote. verify_quote checks claims.
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.
| 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".
Claude Desktop — add to claude_desktop_config.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.
referencesource.org/mcp.MIT licensed.
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.
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-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y referencesource-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-joelp22-maker-referencesource": {
"command": "npx",
"args": [
"-y",
"referencesource-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencereferencesource.org works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.