California Bitcoin

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Bitcoin research for AI agents: free answers, specialist Q&A, verification, evidence, timelines.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "California Bitcoin": {
      "url": "https://californiabitcoin.org/mcp?source=official-mcp-registry",
      "transport": "streamable-http"
    }
  }
}

Measured tools (12)

• start_bitcoin_research read-only

  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.

  Parameters:

  • query (required) — string — Bitcoin question or research task to answer using maintained California Bitcoin knowledge.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• select_bitcoin_research_product read-only

  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.

  Parameters:

  • task (required) — string — 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.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• search_bitcoin_knowledge read-only

  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.

  Parameters:

  • query (required) — string — Bitcoin topic, concept, event, person, protocol feature, or research phrase to search.
  • limit — integer — Maximum number of ranked knowledge matches to return.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get_bitcoin_topic read-only

  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.

  Parameters:

  • id (required) — string — Canonical Knowledge Atlas topic identifier, using lowercase letters, numbers, and hyphens.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• answer_bitcoin_question read-only

  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.

  Parameters:

  • query (required) — string — Bitcoin question to answer from maintained California Bitcoin knowledge.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• answer_bitcoin_question_with_evidence

  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.

  Parameters:

  • query (required) — string — Difficult natural-language Bitcoin question requiring an evidence-grade specialist answer.

  Hints: read-only no · destructive no · idempotent no · open-world yes

• check_bitcoin_evidence_checkpoint read-only

  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.

  Parameters:

  • checkpointId (required) — string — Checkpoint identifier returned by a prior California Bitcoin research result.
  • expectedDigest (required) — string — Expected SHA-256 content digest returned with the checkpoint, including the sha256: prefix.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• verify_bitcoin_claim

  PAID 0.10 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.

  Parameters:

  • claim (required) — string — Bitcoin factual claim to verify against maintained source-linked evidence.

  Hints: read-only no · destructive no · idempotent no · open-world yes

• get_bitcoin_evidence_pack

  PAID 0.15 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.

  Parameters:

  • query (required) — string — Bitcoin research question or topic for which to assemble an evidence pack.

  Hints: read-only no · destructive no · idempotent no · open-world yes

• build_bitcoin_timeline

  PAID 0.10 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.

  Parameters:

  • query (required) — string — Bitcoin event, topic, protocol change, policy, or history question to organize chronologically.
  • limit — integer — Maximum number of sourced timeline events to return.
  • toYear — integer — Optional latest calendar year to include in the timeline.
  • fromYear — integer — Optional earliest calendar year to include in the timeline.

  Hints: read-only no · destructive no · idempotent no · open-world yes

• deep_ground_bitcoin

  PAID 0.25 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.

  Parameters:

  • query (required) — string — Difficult Bitcoin research question or topic requiring deeper multi-source grounding.

  Hints: read-only no · destructive no · idempotent no · open-world yes

• batch_bitcoin_research

  PAID 0.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.

  Parameters:

  • items (required) — array — One to twenty Bitcoin research items to process in the batch.

  Hints: read-only no · destructive no · idempotent no · open-world yes

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.