Authentication

Every request to the MCP server must be authenticated with a Bearer token.

POST /mcp
Host: mcp.hypedexer.com
Authorization: Bearer <your_api_key>

Your API key is the bearer token

The bearer is your Hypedexer API key: the same key you already use for the REST API. There is no separate MCP token to generate, and existing API keys work as-is. You can create and manage keys in your dashboard.

There is no anonymous access

A request without a bearer is refused with 401. Every tier needs a key: including for tools that return public Hyperliquid data.

{
  "jsonrpc": "2.0",
  "error": {
    "code": -32000,
    "message": "Unauthorized: send your HypeDexer API key as \"Authorization: Bearer <key>\". Get one at https://www.app.hypedexer.com/."
  },
  "id": null
}

Verify your setup

The health endpoint is public and needs no key: use it to check that the server is reachable from your network:

curl -X 'GET' \
  'https://mcp.hypedexer.com/health'

{ "ok": true, "name": "hypedexer-mcp", "protocol": "stateless" }

To confirm your key itself works, list the tools directly over HTTP:

curl -X 'POST' \
  'https://mcp.hypedexer.com/mcp' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

A valid key returns the tool catalog. A missing or invalid one returns the 401 above: see Errors for the full list of failure modes.

Key types

Most keys are regular Data API keys: they work both for direct REST calls on api.hypedexer.com and through the MCP server. Some keys are restricted to the hosted MCP server. Using one for a direct REST call returns 403 with the reason mcp_only_key: use a Data API key for direct REST integrations, and for the local stdio server.

Rate limits and credits are enforced per key, exactly as they are for REST. See Rate limits & quotas.

Introduction

Setup

Reference

Your API key is the bearer token

There is no anonymous access

Verify your setup

Key types

​Your API key is the bearer token

​There is no anonymous access

​Verify your setup

​Key types

Your API key is the bearer token

There is no anonymous access

Verify your setup

Key types