Hyperliquid Funding

xyz.honeycheckPublished by honeycheck.xyzv1.0.1Updated Oct 24, 2026

Hyperliquid funding, open interest and carry spreads across all 11 venues. Paid per call, x402.

VerifiedSTDIODesktop onlyFinanceData & Analytics

Overview

AI-generated overview

Local MCP server for Hyperliquid funding rates, open interest and carry spreads across 11 venues, with some tools paid per call via x402.

What you can do
  • Retrieve Hyperliquid funding rates across all 11 venues
  • Look up open interest data
  • Compare carry spreads between venues
  • Use free tools without any wallet setup
  • Pay for premium calls per use through x402 when a funded wallet key is configured
When to use it
Useful when you want an assistant to compare perpetual funding rates, open interest and carry opportunities across Hyperliquid venues, and you are willing to pay per call for the paid tools.
Requirements
Runs as a local npm package over stdio on a desktop machine. Free tools need no credentials. Paid tools need PAY_WALLET_KEY, the private key of a funded Circle Gateway wallet holding USDC, plus optional PAY_CHAIN (arc, base, arbitrum or hyperEvm; default arc) and PAY_MAX_USDC_PER_CALL (default 0.05).
Before you install
PAY_WALLET_KEY is a private key for a funded wallet; anyone with it can move the funds, so use a dedicated low-balance wallet. Paid tools spend USDC per call, capped by PAY_MAX_USDC_PER_CALL (default 0.05), and payments go to a third-party x402 endpoint. The manifest lists no tools, so verify what each call costs before enabling payments.

Installation

In SourceWeft

  1. Open Hyperliquid Funding in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 20, 2026

Score

15% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.