Perpetual Funding Rates API MCP Server

Perpetual Funding Rates API MCP server exists for a simple reason — assistants are far more useful when they can act on Perpetual Funding Rates API directly instead of describing what you should do. Perp funding rates across Binance, Bybit, OKX — open interest, sentiment. x402.

What you get

Perpetual funding rates across Binance, Bybit and OKX. Scan every USDT perp ranked by funding in a single call, or query one asset with open interest and predicted next rate. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What the assistant can call

Once Perpetual Funding Rates API is connected, these are the calls the assistant has available:

• perp_get_funding_rates — GET

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the perpetual funding rates api mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Perpetual Funding Rates API's toolset — perp_get_funding_rates — is a fair guide to whether it matches your workflow. It is maintained by Br0ski777; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Perpetual Funding Rates API's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.