TradeHub

net.tichat.tradehubPublished by tradehub.tichat.netOfficial publisherv2.0.0Updated Oct 30, 2026

Perpetual futures trading for AI agents on the user's own exchange accounts, behind one risk gate.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP server that lets an AI assistant trade perpetual futures on the user's own exchange accounts, routed through a single risk gate.

What you can do
  • Trade perpetual futures on the user's own exchange accounts through the server.
  • Route orders through one shared risk gate rather than direct exchange access.
  • No tool list is published, so the exact actions available are not documented in the supplied material.
When to use it
Consider it when you want an assistant to place or manage perpetual futures trades on exchange accounts you already hold, and you want those actions filtered through a risk gate.
Requirements
A remote streamable HTTP endpoint at tradehub.tichat.net; no local package or runtime is needed. OAuth authentication is required, so the user must authorize the connection. Exchange accounts are the user's own.
Before you install
This server can trade perpetual futures, which involves real money and the risk of loss. It acts on the user's own exchange accounts, so granted access may allow orders and position changes. OAuth authorization should be reviewed before connecting, and the published material does not describe the risk gate's limits or what data is shared with the provider.

Installation

In SourceWeft

  1. Open TradeHub 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/net.tichat.tradehub%2Ftradehub/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": {
    "tradehub": {
      "type": "http",
      "url": "https://tradehub.tichat.net/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. v2.0.0LatestOct 30, 2026

Score

56% 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

    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.

  • 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.