Connect your model
Blocklore runs no model for readers. Bring your own: connect your assistant to Blocklore's MCP server and it answers from the same published claims you see here, with their sources and the block heights they were checked at.
Add it to your assistant
Claude Code
In a terminal:
claude mcp add --transport http blocklore https://blocklore.space/mcpClaude (desktop and web)
Settings, Connectors, Add custom connector, with this URL:
https://blocklore.space/mcpCursor
In .cursor/mcp.json:
{
"mcpServers": {
"blocklore": {
"url": "https://blocklore.space/mcp"
}
}
}VS Code
In .vscode/mcp.json:
{
"servers": {
"blocklore": {
"type": "http",
"url": "https://blocklore.space/mcp"
}
}
}Anything else
Any client that speaks MCP over streamable HTTP; no key, no account:
https://blocklore.space/mcpWhat your model can read
Every tool returns data: claims with their sources, quotes and status. Your model does the reading and the writing, and you see what it cites.
- search_claims
- Find published Bitcoin claims by words, best first (BM25 with prefix matching; opcodes such as OP_RETURN are one term). Each result is a claim in brief with its url to cite; call get_claim for its sources, quotes and checks. Superseded claims are left out.
- get_claim
- One published claim's whole record: the statement, its status and confidence, every source with its tier, locator and exact quote, the checks against the chain and the code, and every revision with what it said before. Cite its url.
- list_topics
- Every published topic with its slug, title, group, lede, how many claims it shows and how many wait for review. Contested and safety topics are marked.
- get_topic
- One topic's sections in reading order, each claim in brief with its depth (curious, user, holder, builder, researcher: from a first look to the specification), and the topic's concept to code ladder of sources.
- list_changes
- Change events newest first: claims created, revised, corrected or superseded, each stamped with the block height and time it was published at. Give since_height to see only what changed after that block.
- get_bip
- One Bitcoin Improvement Proposal as the bitcoin/bips index lists it at a pinned commit: title, layer, type, status, a link to its text at that commit, the published claims that cite it, and every change Blocklore has seen in its index entry.
- list_bips
- The BIP index at a pinned commit, optionally only one status or layer, each BIP with its link at that commit and the ids of the claims citing it.
Keep your model honest
- Ask it to cite claim ids and to say when Blocklore has no claim on a question. Each id opens at https://blocklore.space/claims/<id> with its sources.
- Contested claims carry their status and who holds each position. A model that turns them into one answer is going past what the claims say.
- Missing something? Suggest it for research.
Other ways in
- The JSON API and the full export: API and data.
- For crawlers and context windows: llms.txt and llms-full.txt.
- The store itself, as YAML in git: the repository.