California Bitcoin

org.californiabitcoinPublished by californiabitcoin.orgOfficial publisherv1.2.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP endpoint offering AI assistants Bitcoin research: free answers, specialist Q&A, verification, evidence and timelines.

What you can do
  • Answer Bitcoin research questions with free responses
  • Route specialist questions to expert Q&A
  • Verify Bitcoin claims and check supporting evidence
  • Assemble timelines of Bitcoin events and developments
  • No tool list is published, so exact capabilities are only described at a high level
When to use it
Useful when an assistant needs Bitcoin background research, fact-checking of crypto claims, or chronological context on Bitcoin events, without building a data pipeline yourself.
Requirements
A remote streamable HTTP endpoint at californiabitcoin.org; no packages, environment variables or headers are declared, and no authentication is declared.
Before you install
The server is operated by a third party, so research questions and any details in them are sent to that provider. No tool list or documentation is published, so what it can read, write or charge for cannot be confirmed before connecting.

Installation

In SourceWeft

  1. Open California Bitcoin in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/org.californiabitcoin%2Fagent-commerce/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "california-bitcoin": {
      "type": "http",
      "url": "https://californiabitcoin.org/mcp?source=official-mcp-registry"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.2.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.