Carry Console — MCP App

io.github.TheArkofTechPublished by GitHub account TheArkofTechv0.1.0Updated Oct 26, 2026

Read-only visual Hyperliquid carry scan via MCP Apps and x402 v2 Solana USDC.

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

Remote MCP App that renders a read-only Hyperliquid carry opportunity scan, paid per request via x402 v2 Solana USDC.

What you can do
  • Fetch an existing paid carry opportunities result and render a single read-only opportunity view.
  • The upstream HTTP 402 challenge acts as the price and entitlement source, so nothing is returned until payment is authorized.
When to use it
Use when you want a visual, read-only view of Hyperliquid carry scan opportunities inside an assistant and are willing to pay per request in Solana USDC.
Requirements
A remote streamable HTTP endpoint; no local package, environment variables or headers are declared. A Solana USDC payment capability is needed to satisfy the x402 v2 challenge before any data is returned.
Before you install
The tool is paid: the upstream HTTP 402 challenge sets the price and entitlement, and no data is returned before authorization. Payment is made in Solana USDC, so spending occurs per request. The server declares no authentication, and the endpoint is a non-standard host.

Installation

In SourceWeft

  1. Open Carry Console — MCP App 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-console/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-console-app": {
      "type": "http",
      "url": "https://devbox.tail873466.ts.net:10000/mcp/carry-console"
    }
  }
}

README

This repository has no README.

Tools

1

carry_opportunities_ui

Carry Console — paid opportunity scan

Fetch the existing paid /carry/opportunities result and render one read-only opportunity. The upstream HTTP 402 challenge is the price and entitlement source of truth; no data is returned before authorization.

Parametersinteraction

Version history

1
  1. v0.1.0LatestOct 13, 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.