compi

ai.compiPublished by compi.aiOfficial publisherv1.0.0Updated Oct 29, 2026

Connects AI agents to a Hyperliquid account through compi, with user set limits and paper mode.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP server that connects an AI assistant to a Hyperliquid trading account through compi, with user-set limits and a paper mode.

What you can do
  • Connect an assistant to a Hyperliquid account via compi.
  • Work within limits the user sets.
  • Operate in paper mode for simulated activity.
  • No tool list is published, so the exact actions available are not documented here.
When to use it
When you want an AI assistant to interact with a Hyperliquid account under guardrails you define, or to try such workflows in paper mode before using real funds.
Requirements
A remote MCP endpoint at mcp.compi.ai over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared. A compi and Hyperliquid account is implied.
Before you install
It gives an assistant access to a trading account, so real funds may be at risk; rely on the user-set limits and paper mode, and confirm what each action does before enabling live trading. OAuth grants access to the account, and trading activity is handled by compi and Hyperliquid as third parties.

Installation

In SourceWeft

  1. Open compi in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/ai.compi%2Fcompi/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "compi": {
      "type": "http",
      "url": "https://mcp.compi.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

67% 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 listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.