referencesource.org
REMOTE · REFERENCESOURCE.ORG · 2 COMPONENTS · SCANNED SEP 21
Verified reference data; each record carries its source URL and quote. verify_quote checks claims.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 796 tokens (~199/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the referencesource.org MCP server?
referencesource.org is a hosted endpoint at https://referencesource.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · referencesource.org
claude mcp add --transport http joelp22-maker-referencesource 'https://referencesource.org/mcp'
{
"mcpServers": {
"joelp22-maker-referencesource": {
"url": "https://referencesource.org/mcp"
}
}
} {
"servers": {
"joelp22-maker-referencesource": {
"type": "http",
"url": "https://referencesource.org/mcp"
}
}
} [mcp_servers.joelp22-maker-referencesource] url = "https://referencesource.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"joelp22-maker-referencesource": {
"type": "remote",
"url": "https://referencesource.org/mcp",
"enabled": true
}
}
} openclaw mcp add joelp22-maker-referencesource --url 'https://referencesource.org/mcp' --transport streamable-http
mcp_servers:
joelp22-maker-referencesource:
url: "https://referencesource.org/mcp" {
"McpServers": {
"joelp22-maker-referencesource": {
"Transport": "http",
"Url": "https://referencesource.org/mcp"
}
}
} assistant mcp add joelp22-maker-referencesource -t streamable-http -u 'https://referencesource.org/mcp'
{
"mcpServers": {
"joelp22-maker-referencesource": {
"type": "http",
"url": "https://referencesource.org/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 10 Sept 26 +1
- Stability: 0.97 → pass security
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Sept 26 0
- Tool “list_datasets” rewrote its description, which is the text the model reads security
- Schema quality: 169 → 199 ▼ functional
- “list_datasets” added an optional parameter “full” cosmetic
- “list_datasets” added an optional parameter “query” cosmetic
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://referencesource.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=referencesource.org | CN=WE1,O=Google Trust Services,C=US | 5 Aug 2026 | 3 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 9f260b3a10521b060ef7a85ccbf0f716 |
| SANs: referencesource.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of referencesource.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| referencesource.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://referencesource.org/mcp | Verified | 200 | |
| http (plaintext) | http://referencesource.org/mcp | HTTPS enforced | 301 | https://referencesource.org/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_record Get one record by id ~102
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. Returns the full record with its source URL and verbatim source quote. Record ids appear in search_records results and in each record's url.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_slug | string | yes | Dataset slug from list_datasets. |
| record_id | string | yes | The record's id field, e.g. "ak". |
No output schema declared.
No examples provided.
list_datasets List reference datasets ~178
What reference datasets are available? Lists every published dataset with its title, record count, last-verified date and a one-sentence summary. Covers regulatory thresholds, version compatibility, certification registers, licensing rules and more. Pass `query` to list only the datasets matching a topic — that is much cheaper than reading the whole list. Use the returned slug with search_records or get_record.
| Name | Type | Req | Description |
|---|---|---|---|
| full | boolean | – | Return each dataset's complete scope statement instead of the first sentence. Off by default: the full text is roughly four times the size and is rarely needed to choose a dataset. |
| query | string | – | Optional topic filter, e.g. "boiler", "tariff" or "loan limit". Case-insensitive substring, matched against each dataset's slug, title and full description. Omit it to list every dataset. |
No output schema declared.
No examples provided.
search_records Search records in a dataset ~124
Look up a specific record — search by state name, chemical, certificate number, product name or any keyword. Searches one dataset's records (case-insensitive substring match across all fields). Returns up to 20 matching records, each with its url, source and verbatim source_quote so the answer can be checked.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_slug | string | yes | Dataset slug from list_datasets, e.g. "graduated-driver-licensing". |
| query | string | yes | Substring to match, case-insensitive, e.g. a state code, chemical name or standard number. |
No output schema declared.
No examples provided.
verify_quote Check a claimed value against a record ~234
Is this value actually right? Check a claimed fact against a published record instead of trusting it. Reports whether the claim matches the record's stored value (exact, case-insensitive or normalised — the match type is named), whether it appears in the record's verbatim source quote, and returns the source URL and quote so the claim can be traced upstream. Use this whenever you want to confirm a number, date, threshold or status before stating it. Verdicts: matches_record, matches_quote, differs or not_found.
| Name | Type | Req | Description |
|---|---|---|---|
| claimed_value | string | yes | The value to check, exactly as claimed, e.g. "$832,750" or "no passengers younger than 21". |
| dataset_slug | string | yes | Dataset slug from list_datasets. |
| field | string | – | Field name to check the claim against, e.g. "limit_1_unit". Without it, every stored field is checked. |
| record_id | string | – | The record's id, if known (shown in search_records results and in each record's url). Without it, the dataset's stored values are searched for the claimed value. |
No output schema declared.
No examples provided.
What is the referencesource.org MCP server?
referencesource.org is an MCP server listed in the public MCP registry as io.github.joelp22-maker/referencesource. Verified reference data; each record carries its source URL and quote. verify_quote checks claims. This page covers its hosted endpoint (https://referencesource.org/mcp).
Is the referencesource.org MCP server safe to use?
referencesource.org scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the referencesource.org MCP server expose?
referencesource.org exposes 4 tools: list_datasets, search_records, get_record, verify_quote. Their descriptions and schemas cost roughly 638 tokens of context every time the server is loaded.
Does the referencesource.org MCP server require authentication?
No. We connected to referencesource.org without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the referencesource.org MCP server still maintained?
referencesource.org is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.