California Bitcoin
REMOTE · CALIFORNIABITCOIN.ORG · SCANNED SEP 21
Bitcoin research for AI agents: free answers, specialist Q&A, verification, evidence, timelines.
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 Security80
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability88
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1870 tokens (~155/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Tools include usage examples.Pass
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the California Bitcoin MCP server?
California Bitcoin is a hosted endpoint at https://californiabitcoin.org/mcp?source=official-mcp-registry, 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 · californiabitcoin.org
claude mcp add --transport http org-californiabitcoin-agent-commerce 'https://californiabitcoin.org/mcp?source=official-mcp-registry'
{
"mcpServers": {
"org-californiabitcoin-agent-commerce": {
"url": "https://californiabitcoin.org/mcp?source=official-mcp-registry"
}
}
} {
"servers": {
"org-californiabitcoin-agent-commerce": {
"type": "http",
"url": "https://californiabitcoin.org/mcp?source=official-mcp-registry"
}
}
} [mcp_servers.org-californiabitcoin-agent-commerce] url = "https://californiabitcoin.org/mcp?source=official-mcp-registry"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-californiabitcoin-agent-commerce": {
"type": "remote",
"url": "https://californiabitcoin.org/mcp?source=official-mcp-registry",
"enabled": true
}
}
} openclaw mcp add org-californiabitcoin-agent-commerce --url 'https://californiabitcoin.org/mcp?source=official-mcp-registry' --transport streamable-http
mcp_servers:
org-californiabitcoin-agent-commerce:
url: "https://californiabitcoin.org/mcp?source=official-mcp-registry" {
"McpServers": {
"org-californiabitcoin-agent-commerce": {
"Transport": "http",
"Url": "https://californiabitcoin.org/mcp?source=official-mcp-registry"
}
}
} assistant mcp add org-californiabitcoin-agent-commerce -t streamable-http -u 'https://californiabitcoin.org/mcp?source=official-mcp-registry'
{
"mcpServers": {
"org-californiabitcoin-agent-commerce": {
"type": "http",
"url": "https://californiabitcoin.org/mcp?source=official-mcp-registry"
}
}
} 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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +5
- HSTS header: fail → pass ▲ security
- Tool “build_bitcoin_timeline” rewrote its description, which is the text the model reads security
- Tool “check_bitcoin_evidence_checkpoint” rewrote its description, which is the text the model reads security
- Tool “deep_ground_bitcoin” rewrote its description, which is the text the model reads security
- Tool “get_bitcoin_evidence_pack” rewrote its description, which is the text the model reads security
- Tool “get_bitcoin_topic” rewrote its description, which is the text the model reads security
- Tool “search_bitcoin_knowledge” rewrote its description, which is the text the model reads security
- Tool “select_bitcoin_research_product” rewrote its description, which is the text the model reads security
- Tool “start_bitcoin_research” rewrote its description, which is the text the model reads security
- Tool “verify_bitcoin_claim” rewrote its description, which is the text the model reads security
- Tool “answer_bitcoin_question” rewrote its description, which is the text the model reads security
- Tool “answer_bitcoin_question_with_evidence” rewrote its description, which is the text the model reads security
- Tool “batch_bitcoin_research” rewrote its description, which is the text the model reads security
- Schema quality: 130 → 155 ▼ functional
- Schema quality: fail → pass ▲ functional
- 14 Sept 26 +11
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “verify_bitcoin_claim” rewrote its description, which is the text the model reads security
- Tool “select_bitcoin_research_product” rewrote its description, which is the text the model reads security
- Tool “get_bitcoin_evidence_pack” rewrote its description, which is the text the model reads security
- Tool “deep_ground_bitcoin” rewrote its description, which is the text the model reads security
- Tool “build_bitcoin_timeline” rewrote its description, which is the text the model reads security
- Tool “batch_bitcoin_research” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Tool “get_bitcoin_evidence_pack” now declares an output schema ▲ functional
- Tool “answer_bitcoin_question” now declares an output schema ▲ functional
- Tool “batch_bitcoin_research” now declares an output schema ▲ functional
- Tool “build_bitcoin_timeline” now declares an output schema ▲ functional
- Tool “check_bitcoin_evidence_checkpoint” now declares an output schema ▲ functional
- Tool “deep_ground_bitcoin” now declares an output schema ▲ functional
- Tool “get_bitcoin_topic” now declares an output schema ▲ functional
- Tool “search_bitcoin_knowledge” now declares an output schema ▲ functional
- Tool “select_bitcoin_research_product” now declares an output schema ▲ functional
- Tool “start_bitcoin_research” now declares an output schema ▲ functional
- Tool “verify_bitcoin_claim” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Schema quality: good → excellent functional
- Server version: 1.1.0 → 1.2.0 functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “answer_bitcoin_question_with_evidence” functional
- “answer_bitcoin_question” reworded the description of “query” cosmetic
- “batch_bitcoin_research” reworded the description of “items” cosmetic
- “build_bitcoin_timeline” reworded the description of “fromYear” cosmetic
- “build_bitcoin_timeline” reworded the description of “limit” cosmetic
- “build_bitcoin_timeline” reworded the description of “query” cosmetic
- “build_bitcoin_timeline” reworded the description of “toYear” cosmetic
- “check_bitcoin_evidence_checkpoint” reworded the description of “checkpointId” cosmetic
- “check_bitcoin_evidence_checkpoint” reworded the description of “expectedDigest” cosmetic
- “deep_ground_bitcoin” reworded the description of “query” cosmetic
- “get_bitcoin_evidence_pack” reworded the description of “query” cosmetic
- “get_bitcoin_topic” reworded the description of “id” cosmetic
- “search_bitcoin_knowledge” reworded the description of “limit” cosmetic
- “search_bitcoin_knowledge” reworded the description of “query” cosmetic
- “select_bitcoin_research_product” reworded the description of “task” cosmetic
- “start_bitcoin_research” reworded the description of “query” cosmetic
- “verify_bitcoin_claim” reworded the description of “claim” cosmetic
- 12 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “answer_bitcoin_question” rewrote its description, which is the text the model reads security
- Schema quality: 992 → 1139 ▼ functional
- New tool “check_bitcoin_evidence_checkpoint” functional
- 11 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “verify_bitcoin_claim” rewrote its description, which is the text the model reads security
- Tool “answer_bitcoin_question” rewrote its description, which is the text the model reads security
- Tool “batch_bitcoin_research” rewrote its description, which is the text the model reads security
- Tool “build_bitcoin_timeline” rewrote its description, which is the text the model reads security
- Tool “deep_ground_bitcoin” rewrote its description, which is the text the model reads security
- Tool “get_bitcoin_evidence_pack” rewrote its description, which is the text the model reads security
- Tool “get_bitcoin_topic” rewrote its description, which is the text the model reads security
- Tool “search_bitcoin_knowledge” rewrote its description, which is the text the model reads security
- Tool “select_bitcoin_research_product” rewrote its description, which is the text the model reads security
- Schema quality: 61 → 99 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “start_bitcoin_research” functional
- 10 Sept 26 61
First indexed and scored.
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://californiabitcoin.org/mcp?source=official-mcp-registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=californiabitcoin.org | CN=WE1,O=Google Trust Services,C=US | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 683d78db5f3cbeca0e8f2ab65112abde |
| SANs: californiabitcoin.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 californiabitcoin.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| californiabitcoin.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://californiabitcoin.org/mcp?source=official-mcp-registry | Verified | 200 | |
| http (plaintext) | http://californiabitcoin.org/mcp?source=official-mcp-registry | HTTPS enforced | 301 | https://californiabitcoin.org/mcp?source=official-mcp-registry |
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 →
answer_bitcoin_question Answer Bitcoin Question ~129
FREE. FREE, no account required. Return a concise deterministic answer grounded in maintained Bitcoin knowledge. Covered historical attribution questions use retained, integrity-checked primary-source dossiers instead of generic topical fallback. Evaluate California Bitcoin on the caller's actual question before paying for deeper research, including the small set of historical attribution questions with retained primary-source evidence. Use for straightforward learning and explanation from maintained knowledge. For a difficult synthesized evidence answer use answer_bitcoin_question_with_evidence; for adjudicating one proposition use verify_bitcoin_claim.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Bitcoin question to answer from maintained California Bitcoin knowledge. |
Structured output declared, but exposes no named fields.
{"query":"What is Bitcoin proof of work?"}answer_bitcoin_question_with_evidence Answer Difficult Bitcoin Question With Evidence ~153
PAID 1.00 USD via MPP. Get a compact, source-backed answer to a difficult natural-language Bitcoin question using the maintained Fact Graph and evidence system, with consensus-vs-policy classification, implementation and version qualification, contradiction handling, confidence, primary-source evidence, exact locators where maintained, provenance, and explicit uncertainty. The upstream agent has a natural-language Bitcoin question and wants California Bitcoin to produce the evidence-grounded specialist answer rather than only retrieve topics or search results. Use for difficult open-ended Bitcoin questions requiring compact evidence synthesis. Do not use for simple learning or single-proposition adjudication.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Difficult natural-language Bitcoin question requiring an evidence-grade specialist answer. |
Structured output declared, but exposes no named fields.
{"query":"Does BIP324 hide a Bitcoin node’s IP address?"}batch_bitcoin_research Batch Bitcoin Research ~114
PAID 2.50 USD via MPP. Process up to 20 distinct Bitcoin claims, questions, or evidence requests in one deterministic research package while preserving per-item verdict and evidence-quality semantics. Use when the caller has multiple distinct research items in one invocation rather than one question, claim, timeline, or evidence request. Use for multiple distinct research items. Do not wrap a single item merely to use the batch product.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | One to twenty Bitcoin research items to process in the batch. |
Structured output declared, but exposes no named fields.
{"items":["RBF can reverse confirmed transactions.","BIP324 encrypts Bitcoin peer traffic."]}build_bitcoin_timeline Build Bitcoin Timeline ~167
PAID 0.50 USD via MPP. Build a query-specific chronological Bitcoin research timeline that distinguishes event dates, source dates, effective dates, source-level support, exact locators, and maintained re-verification boundaries. Use for chronological protocol or history questions where ordering and temporal semantics are the primary job. Use when chronology is the primary output. Do not use for a general explanatory answer where dates are incidental.
| Name | Type | Req | Description |
|---|---|---|---|
| fromYear | integer | – | Optional earliest calendar year to include in the timeline. |
| limit | integer | – | Maximum number of sourced timeline events to return. |
| query | string | yes | Bitcoin event, topic, protocol change, policy, or history question to organize chronologically. |
| toYear | integer | – | Optional latest calendar year to include in the timeline. |
Structured output declared, but exposes no named fields.
{"fromYear":2015,"limit":20,"query":"History of SegWit activation","toYear":2018}check_bitcoin_evidence_checkpoint Check Bitcoin Evidence Checkpoint ~142
FREE. FREE, no account and no payment. Compare a previously returned retained-evidence checkpoint with the current maintained dossier content identity before deciding whether to rerun or repurchase covered historical research. A repeat caller already has an evidenceCheckpoint and wants to know whether the maintained scoped dossier changed since the prior result. Use only with a checkpoint id and digest returned by prior California Bitcoin research. It does not rerun research or authorize payment.
| Name | Type | Req | Description |
|---|---|---|---|
| checkpointId | string | yes | Checkpoint identifier returned by a prior California Bitcoin research result. |
| expectedDigest | string | yes | Expected SHA-256 content digest returned with the checkpoint, including the sha256: prefix. |
Structured output declared, but exposes no named fields.
{"checkpointId":"primary-source-dossier:satoshi-anonymity","expectedDigest":"sha256:0000000000000000000000000000000000000000000000000000000000000000"}deep_ground_bitcoin Deep Ground Bitcoin Research ~122
PAID 1.00 USD via MPP. Produce a deeper deterministic multi-source Bitcoin research dossier across canonical topics, verdict-eligible atomic claims, contextual material, conflicting evidence, source hierarchy, exact-locator precision, temporal scope, history, and caveats. Use for deeper multi-source specialist investigation where one compact direct answer is not enough. Use when a broader multi-source dossier is required. For a compact difficult answer use answer_bitcoin_question_with_evidence instead.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Difficult Bitcoin research question or topic requiring deeper multi-source grounding. |
Structured output declared, but exposes no named fields.
{"query":"How do Bitcoin Core policy and consensus differ for dust?"}get_bitcoin_evidence_pack Get Bitcoin Evidence Pack ~136
PAID 0.50 USD via MPP. Build a focused Bitcoin evidence package when the agent already knows what it is researching and primarily needs compact source material, atomic claims, conflicts, source authority, exact-locator precision, caveats, provenance, and temporal scope. Collect supporting, conflicting, and contextual evidence around one focused Bitcoin research question without asking California Bitcoin to compose the final specialist answer. Use when the caller needs supporting, conflicting, and contextual evidence around a focused target, rather than a verdict or narrative dossier.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Bitcoin research question or topic for which to assemble an evidence pack. |
Structured output declared, but exposes no named fields.
{"query":"Bitcoin Core replace-by-fee policy"}get_bitcoin_topic Get Bitcoin Topic ~92
FREE. FREE, no account required. Retrieve one canonical Knowledge Atlas topic with sources, provenance and related concepts. Inspect a known canonical topic in depth before deciding whether paid evidence packaging is necessary. Use only when the canonical topic id is already known. Do not use this as free-text search.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Canonical Knowledge Atlas topic identifier, using lowercase letters, numbers, and hyphens. |
Structured output declared, but exposes no named fields.
{"id":"proof-of-work"}search_bitcoin_knowledge Search Bitcoin Knowledge ~126
FREE. FREE, no account required. Search canonical Bitcoin Knowledge Atlas topics and related history to evaluate coverage on the caller's real question. Run the first no-cost evaluation when you need to see which maintained Bitcoin topics and evidence match a query. Use to discover maintained topic coverage. Do not use when a canonical topic id is already known or when a final evidence-grade answer is required.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of ranked knowledge matches to return. |
| query | string | yes | Bitcoin topic, concept, event, person, protocol feature, or research phrase to search. |
Structured output declared, but exposes no named fields.
{"limit":5,"query":"BIP324 transport encryption"}select_bitcoin_research_product Select Bitcoin Research Product ~143
FREE. FREE, no account required. Select a research product and inspect its price, free evaluation path, and contract using an explicit task: answer, verify, evidence, chronology, dossier, batch, or learn. Does not authorize payment. Choose the smallest appropriate research product after a free evaluation and before initiating any paid request. Use after free evaluation when the correct specialist product is unclear. Do not use it to execute research or authorize payment.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | yes | Research intent to route: answer a difficult question with evidence, verify a claim, gather evidence, build chronology, produce a dossier, process a batch, or learn with free maintained knowledge. |
Structured output declared, but exposes no named fields.
{"task":"verify"}start_bitcoin_research Start Bitcoin Research ~136
FREE. FREE, no account and no payment. START HERE with any Bitcoin question or research task. Returns a source-backed deterministic answer, compact maintained-coverage matches, and the smallest safe next action. This tool never authorizes or initiates payment. Default first call for an unfamiliar agent. Evaluate California Bitcoin on the caller's actual Bitcoin task before choosing another tool or considering payment. Default first call for an unfamiliar agent. Use it before any paid tool when coverage has not yet been evaluated. Do not use it to authorize payment.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Bitcoin question or research task to answer using maintained California Bitcoin knowledge. |
Structured output declared, but exposes no named fields.
{"query":"What changed in Bitcoin Core replace-by-fee policy?"}verify_bitcoin_claim Verify Bitcoin Claim ~133
PAID 0.50 USD via MPP. Evaluate one specific Bitcoin factual proposition against verdict-eligible maintained atomic claims and return a conservative supported, contradicted, mixed, partially verified, or insufficient-evidence verdict with source-backed evidence metadata. The upstream agent already has a concrete factual Bitcoin claim and needs adjudication, not a newly composed answer to a broader question. Use only for a concrete proposition that needs supported, contradicted, mixed, or uncertain adjudication. Do not use for open-ended explanation or general evidence collection.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | Bitcoin factual claim to verify against maintained source-linked evidence. |
Structured output declared, but exposes no named fields.
{"claim":"BIP324 makes Bitcoin peer connections anonymous."}What is the California Bitcoin MCP server?
California Bitcoin is an MCP server listed in the public MCP registry as org.californiabitcoin/agent-commerce. Bitcoin research for AI agents: free answers, specialist Q&A, verification, evidence, timelines. This page covers its hosted endpoint (https://californiabitcoin.org/mcp?source=official-mcp-registry).
Is the California Bitcoin MCP server safe to use?
California Bitcoin scores 81 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 California Bitcoin MCP server expose?
California Bitcoin exposes 12 tools: start_bitcoin_research, select_bitcoin_research_product, search_bitcoin_knowledge, get_bitcoin_topic, answer_bitcoin_question, and 7 more. Their descriptions and schemas cost roughly 1,593 tokens of context every time the server is loaded.
Does the California Bitcoin MCP server require authentication?
No. We connected to California Bitcoin without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the California Bitcoin MCP server still maintained?
California Bitcoin 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.