Bloxwap MCP server

Bloxwap runs a Model Context Protocol server at https://bloxwap.com/mcp over Streamable HTTP. It is unauthenticated, like the rest of the public read surface — point a client at the URL and start calling.

Tools

search_docs(query, limit?, section?)

Search Bloxwap’s documentation, guides and blog. Returns ranked matches with an excerpt and the canonical URL of each, so an answer can cite its source.

get_doc(path)

Fetch the full markdown of one page by site path, e.g. /docs/fees.

quote_fees(notionalUsd, leverage, genesis?, hlTakerTenthsBps?)

Break down what a round trip costs. The Bloxwap builder fee is exact; the Hyperliquid taker fee is the published default and is flagged as an estimate, because it varies per trader.

What it cannot do

It cannot place, modify or close a trade, and it cannot read anyone’s balances, positions or wallet. That is not a missing feature: Bloxwap is non-custodial, every position is signed by the user’s own embedded wallet and settles on-chain on Hyperliquid, so no server — including this one — can act on a user’s behalf. To trade programmatically, talk to Hyperliquid directly.

Connecting

Any MCP client that speaks Streamable HTTP works. In a client’s config, the server is simply a URL with no auth block:

{
  "mcpServers": {
    "bloxwap": {
      "type": "http",
      "url": "https://bloxwap.com/mcp"
    }
  }
}

The server is stateless and issues no session id. It speaks protocol versions 2025-06-18, 2025-03-26 and 2024-11-05, and negotiates down to whichever the client asks for.

More