Carry Intel — Hyperliquid funding screens

io.github.TheArkofTechPublished by GitHub account TheArkofTechv1.0.3Updated Oct 24, 2026

Read-only Hyperliquid funding screens via x402 v2/Solana; not positions or returns.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Gives an assistant read-only Hyperliquid funding-rate screens, paid per request through x402 v2 on Solana.

What you can do
This remote MCP server exposes read-only Hyperliquid funding screens over a streamable HTTP endpoint. Access is metered through x402 v2 on Solana, so each request is paid for rather than covered by an account login. The description states it does not provide positions or returns, so it is limited to funding-screen data.
When to use it
Worth adding when an assistant needs Hyperliquid funding-rate screening data and the user is willing to pay per request in the x402 v2/Solana flow. It is not intended for portfolio, position, or performance-return questions.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is declared. No authentication, environment variables, or headers are declared, but the x402 v2/Solana payment flow implies a Solana wallet or payment credential and network access to the endpoint.
Before you install
Requests are paid through x402 v2 on Solana, so using the server can spend funds from a wallet; treat any wallet key or signing credential as sensitive. The endpoint is a third-party remote host, so queries go to that operator. Data is limited to funding screens and excludes positions and returns.

Installation

In SourceWeft

  1. Open Carry Intel — Hyperliquid funding screens in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.TheArkofTech%2Fcarry-intel/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "carry-intel-hyperliquid-funding-screens": {
      "type": "http",
      "url": "https://devbox.tail873466.ts.net:10000/mcp"
    }
  }
}

README

This repository has no README.

Tools

4

carry_verdicts

Read-only Hyperliquid funding verdicts for tracked markets, with basis and 24h sample context. Positions, trades, and returns are not verified. Costs $0.10/call via x402.

Takes no parameters.

carry_opportunities

Full-universe Hyperliquid carry scan: every positive-funding perp ranked by spot-hedgeability (real HL spot pair + $10k/day volume). Costs $0.50/call via x402.

Takes no parameters.

carry_digest

Latest daily settled-prints funding digest (markdown) from the public track record. Costs $0.02/call via x402. An older dated sample is free at /carry/digest/free when available.

Takes no parameters.

carry_free_sample

FREE (no payment): previous published funding digest when available, with exact sample and latest-report dates. Use this to verify data quality before paying.

Takes no parameters.

Version history

4
  1. v1.0.3LatestOct 14, 2026
  2. v1.0.2Oct 13, 2026
  3. v1.0.1Oct 12, 2026
  4. v1.0.0Oct 12, 2026

Score

75% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • 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.