carrydesk
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CARRYDESK_API_BASE | No | Base URL of the Carrydesk API. Overrides the default. | https://carry.pelazas.com |
| CARRYDESK_PRIVATE_KEY | No | Private key used by the agent to automatically pay for paid endpoints. Without it, free tools work and paid tools return the price. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| carry_snapshotA | FREE. Cross-sectional funding-carry snapshot for Hyperliquid perps: the top 5 coins on each leg (long = market pays you to hold, short = you get paid to short) plus the carry spread. Delayed 24h. Use this first. |
| carry_methodA | FREE. How the carry ranking is computed -- universe filter, lookback, leg construction -- and the caveats that matter before anyone trades on it. Read this before presenting the numbers as actionable. |
| carry_healthB | FREE. Service health and data freshness. |
| carry_rankingsA | PAID (~$0.05 USDC). Full live cross-sectional funding-carry ranking across every liquid Hyperliquid perp: trailing 14d mean funding annualized, rank, long/short leg and dollar-neutral weights, plus outlier-robust spread variants. Set k to change coins per leg (1-20). |
| carry_historyA | PAID (~$0.02 USDC). Archived rank and trailing funding history for one coin, from carrydesk's own published snapshots. Use to check whether a coin's carry is persistent or a one-day artifact. |
| carry_universeA | PAID (~$0.01 USDC). The liquid Hyperliquid perp universe sorted by daily notional volume, with open interest, mark price and current funding. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/pelazas/carrydesk'
If you have feedback or need assistance with the MCP directory API, please join our Discord server