Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Nothing to run from here
California Bitcoin is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
12
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Bitcoin research for AI agents: free answers, specialist Q&A, verification, evidence, timelines.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http california-bitcoin-mcp 'https://californiabitcoin.org/mcp?source=official-mcp-registry'
# 2 — ask your agent for something these tools do
# start_bitcoin_research, select_bitcoin_research_product, search_bitcoin_knowledge and 9 more
California Bitcoin costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CAAll 1 server
californiabitcoin1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http california-bitcoin-mcp 'https://californiabitcoin.org/mcp?source=official-mcp-registry'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Bitcoin question or research task to answer using maintained California Bitcoin knowledge. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
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 answe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Bitcoin topic, concept, event, person, protocol feature, or research phrase to search. |
| limit | integer | no | Maximum number of ranked knowledge matches to return. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Canonical Knowledge Atlas topic identifier, using lowercase letters, numbers, and hyphens. |
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 question
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Bitcoin question to answer from maintained California Bitcoin knowledge. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Difficult natural-language Bitcoin question requiring an evidence-grade specialist answer. |
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 d
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| claim | string | yes | Bitcoin factual claim to verify against maintained source-linked evidence. |
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 B
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Bitcoin research question or topic for which to assemble an evidence pack. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Bitcoin event, topic, protocol change, policy, or history question to organize chronologically. |
| fromYear | integer | no | Optional earliest calendar year to include in the timeline. |
| toYear | integer | no | Optional latest calendar year to include in the timeline. |
| limit | integer | no | Maximum number of sourced timeline events to return. |
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-so
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Difficult Bitcoin research question or topic requiring deeper multi-source grounding. |
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 sing
| Parameter | Type | Required | Notes |
|---|---|---|---|
| items | array | yes | One to twenty Bitcoin research items to process in the batch. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install California Bitcoin or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.2.0.
1.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish California Bitcoin can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.