x402 funding
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_funding_divergenceA | Returns the perpetual funding-rate divergence between Hyperliquid and a liquid CEX benchmark (Binance, or OKX where Binance restricts the region), annualised with each venue's real funding interval, for pairs liquid on both legs, with the direction of the basis trade to open. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so no selection ambiguity is possible. Its purpose—perpetual funding-rate divergence between Hyperliquid and a CEX benchmark—is clearly stated.
The single name follows a clear snake_case verb_noun convention (get_funding_divergence). With one tool there is no pattern to violate.
One tool is thin for a server that implies a funding/basis analytics domain, leaving an agent with no adjacent operations. It is defensible if the server is intentionally a single-signal endpoint, but it sits at the borderline of the 1-2 tool range.
The surface offers a single derived metric with no way to list supported pairs, fetch historical funding series, or adjust venue/pair parameters beyond what the description implies. An agent needing funding data over time or across more venues hits a dead end immediately.