Skip to main content
Nikiwa runs a Model Context Protocol (MCP) server that exposes its blockchain wallet, token, transaction, and prediction-market tools to any MCP-compatible client, including Claude, ChatGPT, and your own agents. Once connected, your assistant can query on-chain data directly and reason over the results.

​
Server details

Endpoint

https://pro-api.nikiwa.com/mcp

Transport

Streamable HTTP

Server name

nikiwa-tools

Auth

OAuth or Bearer API key

​
What the server exposes

Nikiwa exposes blockchain data as deterministic tools. As the server describes itself to clients:
Nikiwa exposes blockchain wallet, token, transaction, and prediction-market data as deterministic tools. It does NOT route, interpret, or synthesize. Each tool returns structured data and YOU compose and reason over the results.
Alongside tools, the server provides:
  • Resources, including nikiwa://chains (the valid network list) and nikiwa://usage (composition recipes), which clients can read to ground their calls.
  • Prompts, ready-made composition recipes for common multi-tool questions.
See the full tool catalog.
The MCP server exposes the full tool set. The public Tools API exposes only a curated subset.

​
Two ways to authenticate

OAuth (recommended)

Best for interactive clients such as Claude and ChatGPT. Sign in and approve a consent screen. There is no key to copy or store.

API key

Best for scripts and self-hosted agents. Pass a developer key as a Bearer token.

​
Using tools well

  • Provide exact entities: a wallet, token, or contract address, a transaction hash, and a network. Tools are deterministic and do not guess.
  • Resolve first: if you only have a symbol, call resolve_token_symbol; for an ENS name, call resolve_ens.
  • Read nikiwa://chains for the valid network list rather than hard-coding it.
  • Each tool returns its data object, {status: no_data}, or {status: error}.