MCP server

The API beta is live. Sign in at noxint.ai/dashboard to mint a personal key and fund data credits; paid REST and MCP calls settle for real. The discovery surface never needed a key: run curl https://noxint.ai/api/v1 right now and the contract answers. Launch status is the ledger of what is on.

Noxint is a native Model Context Protocol server at https://noxint.ai/api/mcp: the same 23 operations, the same parameters, the same data-credit billing, and the same idempotency ledger as the HTTP API, exposed as MCP tools. If you already run an MCP client, this is the fastest way to hand an agent live market data. The transport is stateless streamable HTTP in JSON response mode. Every request is a POST and must send Content-Type: application/json and an Accept header that includes both application/json and text/event-stream.

Client configuration

Claude Code
Cursor
Other clients

claude mcp add --transport http noxint https://noxint.ai/api/mcp \
  --header "Authorization: Bearer nx_your_key"

{
  "mcpServers": {
    "noxint": {
      "url": "https://noxint.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer nx_your_key"
      }
    }
  }
}

Point any streamable-HTTP MCP client at https://noxint.ai/api/mcp with the key in an Authorization: Bearer header. In Claude Desktop, add the URL as a custom connector in Settings.

Methods

The server supports initialize, ping, tools/list, tools/call, resources/list, resources/read, and resources/templates/list. Discovery (initialize, tools/list) is keyless. The documentation sections are also exposed as resources under noxint://docs/<section>, so an agent can read the manual over the same wire it trades data on. The supported protocol versions are 2025-11-25 (latest), 2025-06-18, and 2025-03-26. The server reports itself as noxint-market-data, version 1.0.0.

Tools

Exactly 23 tools, one per operation, each named identically to its HTTP operation (read, funding, financials, and so on). Each tool takes the same parameters as the operation and is marked read-only and idempotent. tools/list returns every tool with its input schema, so an agent discovers the full surface without a key and without a human writing glue code. Only docs and schema are fully keyless. resolve, coverage, and usage authenticate but cost nothing. Every other tool spends data credits exactly as the HTTP operation does.

Authentication

Paid tool calls send the personal key as an Authorization: Bearer header on the POST. Authentication happens inside tools/call. A paid tool called without a key returns a tool result with an unauthenticated error and isError set, rather than a transport-level failure, so agent loops degrade cleanly instead of crashing.

Example tool call

A tools/call request names the tool and passes its arguments. String-list arguments such as ids are joined with commas, matching the HTTP query.

curl -X POST 'https://noxint.ai/api/mcp' \
  -H 'Authorization: Bearer nx_your_key' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"read","arguments":{"id":"crypto:bitcoin"}}}'

The result carries the envelope in structuredContent, a text rendering in content, and an isError flag:

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [{ "type": "text", "text": "{\"data\":{...}}" }],
    "structuredContent": {
      "data": {
        "asset_id": "crypto:bitcoin",
        "status": "live",
        "next_update_at": "2026-07-16T09:45:19Z",
        "headline": { "price_usd": 64068, "funding_rate_8h_pct": { "value": 0.0065, "pctl": 84.4 } }
      }
    },
    "isError": false
  }
}

Billing and idempotency

MCP and HTTP share one idempotency namespace per personal key and normalized operation, so an MCP retry can replay a result first produced over HTTP, and it is charged once. Unlike HTTP, MCP has no conditional-header loop, so re-calling the same tool always spends credits again. Cache the last result and respect next_update_at: the payload tells you when a re-call can say anything new.

Using the API

Guides

Operations

MCP

Client configuration

Methods

Tools

Authentication

Example tool call

Billing and idempotency

​Client configuration

​Methods

​Tools

​Authentication

​Example tool call

​Billing and idempotency

Client configuration

Methods

Tools

Authentication

Example tool call

Billing and idempotency