Carrydesk MCP server
io.github.pelazas/carrydesk·v0.1.2Funding-carry rankings for Hyperliquid perps, metered per call in USDC via x402.
0 stars24 downloads/wk
Reviews
Write oneNobody has reviewed Carrydesk yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Carrydesk tools (6)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
carry_healthFREE. Service health and data freshness.
carry_historycarry_methodcarry_rankingscarry_snapshotcarry_universe
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- Code scan17 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 23 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Carrydesk compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 83/100
- higher than 65% of 48,255 servers
- Tools
- 6
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 24
- more than 10% of 12,191 servers with a package
What its tools let an agent do: 6 read
Install Carrydesk in Claude Code, Cursor or VS Code
claude mcp add carrydesk -- uvx carrydesk
What the publisher says
From the Carrydesk repository's README, as published. We do not edit it. Read it on GitHub
carrydesk
<!-- mcp-name: io.github.pelazas/carrydesk -->
Cross-sectional funding-carry rankings for Hyperliquid perpetuals, sold per call in USDC.
Every hour, rank the liquid Hyperliquid perp universe by trailing 14-day mean funding. The most negative names pay you to hold them long; the most positive pay you to short them. The spread between those two legs is the carry — a structural risk premium, not a prediction.
This is the same signal a live market-neutral book trades, published as an API.
Endpoints
Paid endpoints are metered with x402: the server answers 402 with payment requirements, your client pays USDC on Base, retries, and gets the data. No account, no API key, no invoice.
Quick start
curl -s https://carry.pelazas.com/v1/free/carry | jq{
"carry_spread_annualized": 0.3901,
"carry_spread_annualized_trimmed": 0.2231,
"carry_spread_annualized_median": 0.0955,
"headline_vs_typical": 4.09,
"outlier_dominated": true,
"longs": [{"coin": "PENGU", "mean_funding_annualized": -0.0636}, ...],
"shorts": [{"coin": "SAGA", "mean_funding_annualized": 1.9886}, ...]
}Three spread numbers, always, plus two that say how far apart they are. The headline mean is what an equal-weighted book earns; the median is what a typical coin pays. headlinevstypical is the multiple between them — about 4 in the sample above, and around 4 in practice — and outlier_dominated fires when the median drops below half the mean. On the reading above, SAGA alone accounts for most of the gap — that is exactly the kind of thing a single number would hide.
MCP
claude mcp add carrydesk -- uvx --from carrydesk carrydesk-mcpNo clone, no virtualenv — uvx fetches and runs it.
Six tools: carrysnapshot, carrymethod, carryhealth (free) and carryrankings, carryhistory, carryuniverse (paid). It talks to https://carry.pelazas.com by default — override with CARRYDESKAPIBASE.
Set CARRYDESKPRIVATEKEY to let the agent pay automatically. Without it the free tools work and paid tools return the price instead of failing, so a wallet-less install is still useful.
Local development
uv venv --python 3.12 && uv pip install -e ".[dev]"
.venv/bin/python -m uvicorn carrydesk.api:app --reload # open, no paywall
.venv/bin/python -m pytest -q # full suite, no networkWith X402PAYTO unset the service runs fully open — that is the dev default. Set it to turn the paywall on. See .env.example.
For agents and crawlers
/llms.txt describes the whole service in plain text. /openapi.json is the full spec, /archive is every snapshot ever published, and the public page carries schema.org Dataset markup. Crawlers are explicitly welcome — the free tier exists to be read, indexed and quoted.
Honest limitations
absorbing crowded leverage, not a forecast.
- The carry spread can and does go negative. This is compensation for
erase the edge; the reference book is maker-only for that reason.
- All figures are gross of fees, slippage and borrow. Taker fees alone can
trimmed and median variants before sizing anything.
- Funding is Hyperliquid's own, with no cross-venue reconciliation yet.
- Illiquid names dominate the headline spread more often than not. Read the
- Informational only. Not investment advice.
Repo docs
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Carrydesk: common questions
- Is Carrydesk MCP server safe?
- Mostly: it is graded B (83/100). Read the Carrydesk safety report
- How do I install Carrydesk?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Carrydesk need an API key?
- Yes. The registry entry asks for
CARRYDESK_PRIVATE_KEY. - Is Carrydesk maintained?
- The last commit was 64 days ago (2026-09-01). The latest release is v0.1.2.
- How does Carrydesk compare with other MCP servers?
- safety score 83/100 (higher than 65% of 48,255 servers); tools 6 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.