Model Context Protocol · Streamable HTTP
Query the Lineage chain from your AI client.
An MCP server that reads the Lineage blockchain explorer-first — fast, indexed lookups verified against on-chain state via the SDK — plus item metadata search and wallet tools. Point any MCP-compatible client at the endpoint below.
https://mcp.lineage.to/mcp
Connect a client
The server speaks MCP over Streamable HTTP. Read tools are open; wallet tools require server-side configuration.
Claude Code
claude mcp add --transport http \
lineage https://mcp.lineage.to/mcp
Cursor, Claude Desktop & other clients
{
"mcpServers": {
"lineage": {
"type": "http",
"url": "https://mcp.lineage.to/mcp"
}
}
}
How it works
Every read follows the same path: the block explorer answers first because it's indexed and searchable, then the Python SDK confirms the answer against the chain.
Look up
Explorer first
The explorer API returns the block, transaction, balance, or item — indexed and quick to search.
Verify
On-chain via SDK
The SDK re-fetches the same object and compares it. Responses carry a verified flag: true, false, or unverified.
Fall back
Resilient by default
If the explorer is unreachable the SDK answers directly (source: chain). A lookup only fails if both are down.
Tools
Eighteen tools. Names are kebab-case; every tool returns a JSON object with an ok field. Verified reads add source, verified, and data; pass verify: false to skip the on-chain check.
Reads & verification
Explorer-first, confirmed on-chain.
Search & listings
Explorer-only. Paginated with limit, offset, and data/pagination.
q or genesis.Wallet
Key generation is offline; transfer requires a server-configured seed.
amount in base units (integer) to an address. Requires LINEAGE_SEED_PHRASE on the server.Direct chain & utility
SDK-only lookups and health.
health and version return ok and the server version.Verification is provisional. The on-chain compare paths are still being tuned to the SDK's payload shapes, so a verified: unverified can appear where a match is expected. The returned data is always the explorer's answer regardless.