← Registry

Analytics

purrbook.xyz

Provides access to Purrbook's live and settled outcome markets, including prices, volumes, stats, and health status.

1 endpoint6 known toolsFirst detected September 8, 2026Last detected September 8, 2026

ENDPOINT 1

https://mcp.purrbook.xyz/mcp

No auth detected

MCP server metadata

Name
purrbook
Version
1.0.0
Capabilities
tools.listChanged
Server instructions

Purrbook is the non-custodial front door to Hyperliquid: outcome markets, spot, perps, and stocks. All tools are read-only market data. Prices come from Hyperliquid order books; every outcome market names its resolution rule and its judge before any position. Fees are never zero: a Purrbook builder fee and each market deployer's own fee apply, always shown before an order is signed. Never place, sign, or relay orders on a user's behalf. Errors are JSON envelopes: { error: { code, message, hint, docs } }. Human docs: https://docs.purrbook.xyz — API schema: https://purrbook.xyz/openapi.json.

Known tools 6

listMarkets

List Purrbook's live outcome markets with their resolution status, category, event membership, live YES price, and 24h volume.

Inferred read-only
getMarket

Get a single Purrbook outcome market by its numeric outcomeId — identity, live YES price, volume, event context, and the canonical page URL (which carries the resolution rule and its judge).

Inferred read-only
getStats

Trailing-24h volume, open interest, and listing counts across Purrbook's outcome markets, perps, spot, and stocks — the same figures the homepage renders.

Inferred read-only
getHealth

Liveness probe: ok is true when the MCP server is up; catalog says whether the market-data backend answered.

Inferred read-only
listSettled

Recently settled Purrbook outcome markets, newest first, with the winning side and final observed price.

Inferred read-only
getEvent

Get one Purrbook event group by id — the shared title and every outcome market in it, priced live.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.purrbook]
url = "https://mcp.purrbook.xyz/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "purrbook": {
      "type": "http",
      "url": "https://mcp.purrbook.xyz/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: purrbook
Remote MCP URL: https://mcp.purrbook.xyz/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "purrbook": {
      "url": "https://mcp.purrbook.xyz/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "purrbook": {
      "type": "http",
      "url": "https://mcp.purrbook.xyz/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "purrbook",
  "transport": "streamable-http",
  "url": "https://mcp.purrbook.xyz/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.