California Bitcoin

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

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
100%
Naming quality
87%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (3)

  • LOWTool 'select_bitcoin_research_product' name length outside 3-30 rangein select_bitcoin_research_product
  • LOWTool 'answer_bitcoin_question_with_evidence' name length outside 3-30 rangein answer_bitcoin_question_with_evidence
  • LOWTool 'check_bitcoin_evidence_checkpoint' name length outside 3-30 rangein check_bitcoin_evidence_checkpoint

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~3,688Tokens (tool definitions)
~2.4 KBTypical response size
Significant attention impact (2.88% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "agent-commerce": {
      "url": "https://californiabitcoin.org/mcp"
    }
  }
}

Remote endpoints

https://californiabitcoin.org/mcpstreamable-http
https://californiabitcoin.org/mcp?source=official-mcp-registrystreamable-http

What it can do

Tool inventory

Tools (12)

🟒 Read-only🟑 WriteπŸ”΄ Deleteβšͺ Unknown
🟒start_bitcoin_research(query)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 1,
      "maxLength": 2000,
      "description": "Bitcoin question or research task to answer using maintained California Bitcoin knowledge.",
      "examples": [
        "What changed in Bitcoin Core replace-by-fee policy?"
      ]
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false,
  "description": "Input for Start Bitcoin Research. Use the documented fields exactly; unknown fields are rejected.",
  "examples": [
    {
      "query": "What changed in Bitcoin Core replace-by-fee policy?"
    }
  ]
}

Output Schema

{
  "type": "object",
  "description": "Structured California Bitcoin result with operation-specific research, evidence, provenance, coverage, freshness, trust, and next-step fields.",
  "additionalProperties": true
}
🟒select_bitcoin_research_product(task)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "task": {
      "type": "string",
      "enum": [
        "answer",
        "verify",
        "evidence",
        "chronology",
        "dossier",
        "batch",
        "learn"
      ],
      "description": "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.",
      "examples": [
        "verify"
      ]
    }
  },
  "required": [
    "task"
  ],
  "additionalProperties": false,
  "description": "Input for Select Bitcoin Research Product. Use the documented fields exactly; unknown fields are rejected.",
  "examples": [
    {
      "task": "verify"
    }
  ]
}

Output Schema

{
  "type": "object",
  "description": "Structured California Bitcoin result with operation-specific research, evidence, provenance, coverage, freshness, trust, and next-step fields.",
  "additionalProperties": true
}
🟒search_bitcoin_knowledge(query, limit)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 1,
      "maxLength": 2000,
      "description": "Bitcoin topic, concept, event, person, protocol feature, or research phrase to search.",
      "examples": [
        "BIP324 transport encryption"
      ]
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 10,
      "default": 5,
      "description": "Maximum number of ranked knowledge matches to return.",
      "examples": [
        5
      ]
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false,
  "description": "Input for Search Bitcoin Knowledge. Use the documented fields exactly; unknown fields are rejected.",
  "examples": [
    {
      "query": "BIP324 transport encryption",
      "limit": 5
    }
  ]
}

Output Schema

{
  "type": "object",
  "description": "Structured California Bitcoin result with operation-specific research, evidence, provenance, coverage, freshness, trust, and next-step fields.",
  "additionalProperties": true
}
🟒get_bitcoin_topic(id)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "pattern": "^[a-z0-9-]+$",
      "maxLength": 120,
      "description": "Canonical Knowledge Atlas topic identifier, using lowercase letters, numbers, and hyphens.",
      "examples": [
        "proof-of-work"
      ]
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false,
  "description": "Input for Get Bitcoin Topic. Use the documented fields exactly; unknown fields are rejected.",
  "examples": [
    {
      "id": "proof-of-work"
    }
  ]
}

Output Schema

{
  "type": "object",
  "description": "Structured California Bitcoin result with operation-specific research, evidence, provenance, coverage, freshness, trust, and next-step fields.",
  "additionalProperties": true
}
🟒answer_bitcoin_question(query)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 1,
      "maxLength": 2000,
      "description": "Bitcoin question to answer from maintained California Bitcoin knowledge.",
      "examples": [
        "What is Bitcoin proof of work?"
      ]
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false,
  "description": "Input for Answer Bitcoin Question. Use the documented fields exactly; unknown fields are rejected.",
  "examples": [
    {
      "query": "What is Bitcoin proof of work?"
    }
  ]
}

Output Schema

{
  "type": "object",
  "description": "Structured California Bitcoin result with operation-specific research, evidence, provenance, coverage, freshness, trust, and next-step fields.",
  "additionalProperties": true
}
🟒answer_bitcoin_question_with_evidence(query)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 1,
      "maxLength": 2000,
      "description": "Difficult natural-language Bitcoin question requiring an evidence-grade specialist answer.",
      "examples": [
        "Does BIP324 hide a Bitcoin node’s IP address?"
      ]
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false,
  "description": "Input for Answer Difficult Bitcoin Question With Evidence. Use the documented fields exactly; unknown fields are rejected.",
  "examples": [
    {
      "query": "Does BIP324 hide a Bitcoin node’s IP address?"
    }
  ]
}

Output Schema

{
  "type": "object",
  "description": "Structured California Bitcoin result with operation-specific research, evidence, provenance, coverage, freshness, trust, and next-step fields.",
  "additionalProperties": true
}
🟒check_bitcoin_evidence_checkpoint(checkpointId, expectedDigest)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "checkpointId": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Checkpoint identifier returned by a prior California Bitcoin research result.",
      "examples": [
        "primary-source-dossier:satoshi-anonymity"
      ]
    },
    "expectedDigest": {
      "type": "string",
      "pattern": "^sha256:[a-f0-9]{64}$",
      "maxLength": 80,
      "description": "Expected SHA-256 content digest returned with the checkpoint, including the sha256: prefix.",
      "examples": [
        "sha256:0000000000000000000000000000000000000000000000000000000000000000"
      ]
    }
  },
  "required": [
    "checkpointId",
    "expectedDigest"
  ],
  "additionalProperties": false,
  "description": "Input for Check Bitcoin Evidence Checkpoint. Use the documented fields exactly; unknown fields are rejected.",
  "examples": [
    {
      "checkpointId": "primary-source-dossier:satoshi-anonymity",
      "expectedDigest": "sha256:0000000000000000000000000000000000000000000000000000000000000000"
    }
  ]
}

Output Schema

{
  "type": "object",
  "description": "Structured California Bitcoin result with operation-specific research, evidence, provenance, coverage, freshness, trust, and next-step fields.",
  "additionalProperties": true
}
🟒verify_bitcoin_claim(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.

Input Schema

{
  "type": "object",
  "properties": {
    "claim": {
      "type": "string",
      "minLength": 1,
      "maxLength": 2000,
      "description": "Bitcoin factual claim to verify against maintained source-linked evidence.",
      "examples": [
        "BIP324 makes Bitcoin peer connections anonymous."
      ]
    }
  },
  "required": [
    "claim"
  ],
  "additionalProperties": false,
  "description": "Input for Verify Bitcoin Claim. Use the documented fields exactly; unknown fields are rejected.",
  "examples": [
    {
      "claim": "BIP324 makes Bitcoin peer connections anonymous."
    }
  ]
}

Output Schema

{
  "type": "object",
  "description": "Structured California Bitcoin result with operation-specific research, evidence, provenance, coverage, freshness, trust, and next-step fields.",
  "additionalProperties": true
}
🟒get_bitcoin_evidence_pack(query)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 1,
      "maxLength": 2000,
      "description": "Bitcoin research question or topic for which to assemble an evidence pack.",
      "examples": [
        "Bitcoin Core replace-by-fee policy"
      ]
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false,
  "description": "Input for Get Bitcoin Evidence Pack. Use the documented fields exactly; unknown fields are rejected.",
  "examples": [
    {
      "query": "Bitcoin Core replace-by-fee policy"
    }
  ]
}

Output Schema

{
  "type": "object",
  "description": "Structured California Bitcoin result with operation-specific research, evidence, provenance, coverage, freshness, trust, and next-step fields.",
  "additionalProperties": true
}
🟒build_bitcoin_timeline(query, fromYear, toYear, limit)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 1,
      "maxLength": 2000,
      "description": "Bitcoin event, topic, protocol change, policy, or history question to organize chronologically.",
      "examples": [
        "History of SegWit activation"
      ]
    },
    "fromYear": {
      "type": "integer",
      "minimum": 1900,
      "maximum": 2200,
      "description": "Optional earliest calendar year to include in the timeline.",
      "examples": [
        2015
      ]
    },
    "toYear": {
      "type": "integer",
      "minimum": 1900,
      "maximum": 2200,
      "description": "Optional latest calendar year to include in the timeline.",
      "examples": [
        2018
      ]
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 40,
      "default": 40,
      "description": "Maximum number of sourced timeline events to return.",
      "examples": [
        20
      ]
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false,
  "description": "Input for Build Bitcoin Timeline. Use the documented fields exactly; unknown fields are rejected.",
  "examples": [
    {
      "query": "History of SegWit activation",
      "fromYear": 2015,
      "toYear": 2018,
      "limit": 20
    }
  ]
}

Output Schema

{
  "type": "object",
  "description": "Structured California Bitcoin result with operation-specific research, evidence, provenance, coverage, freshness, trust, and next-step fields.",
  "additionalProperties": true
}
🟒deep_ground_bitcoin(query)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 1,
      "maxLength": 2000,
      "description": "Difficult Bitcoin research question or topic requiring deeper multi-source grounding.",
      "examples": [
        "How do Bitcoin Core policy and consensus differ for dust?"
      ]
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false,
  "description": "Input for Deep Ground Bitcoin Research. Use the documented fields exactly; unknown fields are rejected.",
  "examples": [
    {
      "query": "How do Bitcoin Core policy and consensus differ for dust?"
    }
  ]
}

Output Schema

{
  "type": "object",
  "description": "Structured California Bitcoin result with operation-specific research, evidence, provenance, coverage, freshness, trust, and next-step fields.",
  "additionalProperties": true
}
🟒batch_bitcoin_research(items)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "items": {
      "type": "array",
      "minItems": 1,
      "maxItems": 20,
      "description": "One to twenty Bitcoin research items to process in the batch.",
      "items": {
        "oneOf": [
          {
            "type": "string",
            "minLength": 1,
            "maxLength": 2000,
            "description": "Bitcoin question, claim, or evidence request as plain text."
          },
          {
            "type": "object",
            "properties": {
              "type": {
                "type": "string",
                "enum": [
                  "question",
                  "claim",
                  "evidence"
                ],
                "default": "question",
                "description": "Research item type: question, factual claim, or evidence request."
              },
              "text": {
                "type": "string",
                "minLength": 1,
                "maxLength": 2000,
                "description": "Bitcoin question, claim, or evidence request text."
              }
            },
            "required": [
              "text"
            ],
            "additionalProperties": false
          }
        ]
      },
      "examples": [
        [
          "RBF can reverse confirmed transactions.",
          "BIP324 encrypts Bitcoin peer traffic."
        ]
      ]
    }
  },
  "required": [
    "items"
  ],
  "additionalProperties": false,
  "description": "Input for Batch Bitcoin Research. Use the documented fields exactly; unknown fields are rejected.",
  "examples": [
    {
      "items": [
        "RBF can reverse confirmed transactions.",
        "BIP324 encrypts Bitcoin peer traffic."
      ]
    }
  ]
}

Output Schema

{
  "type": "object",
  "description": "Structured California Bitcoin result with operation-specific research, evidence, provenance, coverage, freshness, trust, and next-step fields.",
  "additionalProperties": true
}

Recommended Prompts

search_research
Search for information about [topic] using California Bitcoin
Expected tools: start_bitcoin_research
find_specific
Find [specific item] using California Bitcoin
Expected tools: start_bitcoin_research
retrieve_data
Get details about [item] from California Bitcoin
Expected tools: get_bitcoin_topic
fetch_info
Fetch [information type] using California Bitcoin
Expected tools: get_bitcoin_topic
research_workflow
Search for [topic], then get detailed information about the top results using California Bitcoin
Expected tools: start_bitcoin_researchget_bitcoin_topic

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded12 tools
verifiedversion not recorded12 tools
verifiedversion not recorded12 tools
verifiedversion not recorded12 tools