algovesta/mcp

---

AlgoVesta runs a hosted Model Context Protocol server that reaches 16 crypto exchanges and MetaTrader 5 through a single HTTPS endpoint. Claude, ChatGPT, Cursor, Claude Code, Gemini CLI or any other MCP-capable client can read balances, open and close positions, move stop-loss and take-profit, and audit its own actions.

Your risk rules are compiled to JSON and evaluated on the server, after the request leaves the model — outside the reach of anything the model can be persuaded to say. Every new key starts on a $5,000 paper balance, and every action returns an ed25519-signed, hash-chained receipt.

Hosted and closed-source. This repository is the public documentation, tool reference and client configuration set. There is nothing to install, build or self-host — you connect to the hosted endpoint.

Contents — At a glance · How it works · Quick start · Connect your client · Supported AI clients · In use · Tools · Safety model · Venues · Performance and limits · Endpoints · FAQ

At a glance

How it works

flowchart LR
    A["AI clientClaude, ChatGPT, Cursor, and more"]
    B["AlgoVesta MCP serverscope, rate limit, idempotency"]
    C{"Policy wallevaluated server-side"}
    R["Refusalplus audit entry"]
    D["Execution"]
    E["16 crypto exchanges"]
    F["MetaTrader 5managed terminals"]
    G["Paper engine5,000 USD virtual"]
    H["ed25519-signed receipt"]

    A -->|MCP over HTTPS| B
    B --> C
    C -->|violates a rule| R
    C -->|allowed| D
    D --> E
    D --> F
    D --> G
    D --> H

The model is the caller, never the authority. It decides what to ask for; the server decides what happens. Your exchange API keys never leave AlgoVesta and are created without withdrawal permission — the assistant only ever holds a scoped, revocable MCP link.

Quick start

1. Create an AlgoVesta account and open the MCP Connection tab in the panel.
2. Generate a key. New keys default to the paper scope; the full link is shown once.
3. Paste the link into your AI client as a custom MCP server.

https://api.algovesta.com/u/avmcp_/mcp

That URL is a credential. Treat it like a password. If it leaks, revoke it in the panel — revocation takes effect immediately for new connections and drops open event streams within seconds.

Clients that prefer a full authorization flow can use OAuth 2.1 instead, at https://api.algovesta.com/mcp. PKCE (S256) is mandatory and Dynamic Client Registration is supported, so most clients configure themselves. See docs/AUTHENTICATION.md.

Connect your client

Six walkthroughs below; anything else uses the same URL in whatever field it calls a remote MCP server.

Claude — web, desktop, iOS, Android

Settings -> Connectors -> Add custom connector, paste the URL, then allow the tools when Claude asks. Walkthrough

Claude Code

claude mcp add --transport http algovesta https://api.algovesta.com/u/avmcp_/mcp

Walkthrough

ChatGPT

Settings -> Connectors -> Advanced -> Developer mode -> Create, transport Streamable HTTP. Custom connectors are a paid-plan feature on OpenAI’s side. Walkthrough

Cursor

~/.cursor/mcp.json, or .cursor/mcp.json inside a project — file

{
  "mcpServers": {
    "algovesta": { "url": "https://api.algovesta.com/u/avmcp_/mcp" }
  }
}

VS Code — GitHub Copilot

.vscode/mcp.json — file

{
  "servers": {
    "algovesta": {
      "type": "http",
      "url": "https://api.algovesta.com/u/avmcp_/mcp"
    }
  }
}

Gemini CLI

~/.gemini/settings.json — file. CLI only; the Gemini web app does not accept custom MCP servers.

{
  "mcpServers": {
    "algovesta": { "httpUrl": "https://api.algovesta.com/u/avmcp_/mcp" }
  }
}

Anything else

The three config shapes you will meet, plus a curl connection check: examples/other-clients.md

Supported AI clients

This is a standard remote MCP server over Streamable HTTP, so anything that speaks remote MCP can connect. The clients below document that support themselves — each row links to the client’s own configuration docs, which is where the exact field name lives.

Scope of that claim. We have verified Claude end to end against this server. The others are listed because they document remote MCP support — not because we individually tested each one. Client support also moves fast, and a given client may gate connectors behind a paid plan (ChatGPT does) or behind its CLI only (the Gemini web app does not accept custom MCP servers). If a listed client misbehaves with us, or one is missing, open an issue.

What it looks like in use

You never call a tool by name. You ask in plain language; the assistant picks the tool.

And what it will refuse. “Turn on auto-trading for that strategy” — refused; auto_trade is not a writable field in any scope. “Trade on Kraken for me” when Kraken is not connected — VENUE_NOT_CONNECTED, not a guess. “Open it without a stop” — refused, with no saved default to fall back on.

On a paper key every one of those runs against the $5,000 virtual balance with the identical toolset, so the whole workflow can be rehearsed before real money is reachable.

Tools

20 tools. Scope read works on any key; paper / live gates the rest.

Two of them deserve a note, because what they refuse to do is the point:

• compare_venues does not route your order. It reports the live price and, on venues that publish one, the bid/ask spread. It does not know your fee tier, the order book depth or the slippage you would pay — and it says so in every response. A venue that publishes no bid/ask is listed separately rather than ranked as if its spread were zero. You still name the exchange yourself in place_order.
• create_strategy / update_strategy cannot turn real money on. A new strategy is always created with auto_trade off, and auto_trade is not in the writable field set — an assistant cannot set it, whatever it is asked or persuaded to do. A single order is one action you can see; a strategy keeps trading after the conversation ends, so arming one stays a human decision made in the panel. ip_allowlist is refused for the same reason: it is the second factor that verifies where signals come from.

Full reference with descriptions and JSON Schemas: docs/TOOLS.md · machine-readable: tools.json

Safety model

The AI is the caller — never the authority. Full model: docs/SAFETY.md.

Venues

Crypto (16) — Binance · Bybit · OKX · KuCoin · Gate.io · Bitget · Kraken · Coinbase · BingX · Hyperliquid · Backpack · HTX · BloFin · Phemex · WOO X · CoinEx

Forex, metals, indices — MetaTrader 5, zero installation: AlgoVesta runs the MT5 terminals on its own managed servers, connected to your broker 24/7.

Simulation — built-in paper engine, $5,000 virtual.

Six exchanges — Binance, Bybit, OKX, Gate.io, KuCoin and Bitget — have been verified end to end with real money on both futures and spot, with stop-loss and take-profit confirmed on the exchange itself. Each exchange has its own quirks, and the differences are deliberate rather than gaps: Bybit and Bitget do not accept a second take-profit leg on spot; OKX spot is routed through the raw API to keep a cash account from silently becoming a margin account; Binance spot enforces a minimum notional before buying; KuCoin market buys are placed in cost mode. A venue becomes available to the AI only after you connect it — asking for one you have not connected returns VENUE_NOT_CONNECTED rather than a guess.

Performance and limits

Measured, not marketing — figures measured in August 2026; the averages match the ones published on algovesta.com:

Time spent inside your AI client — the model thinking, and you confirming — is not included and usually dominates. This server is not a low-latency execution venue and is not sold as one.

Endpoints

Published in the official MCP Registry as com.algovesta/trading; server.json in this repository is that manifest.

FAQ

Examples

Ready-to-use files in examples/:

• TradingView alert templates: six JSON messages (basic entry, multi take-profit, Pine strategy with position state, close, forex on MT5, crypto with margin and leverage) and the field reference the webhook receiver uses.
• Telegram signal parsing corpus: 30 synthetic signal messages with the expected parse for each, for testing your own copier or seeing which formats the AlgoVesta parser is built for.
• MCP client code: minimal Python and Node.js programs that connect with a secret link, read the portfolio and place a paper order.
• Client configs: Cursor, VS Code, Gemini CLI.

Support

Account and trading questions: support · [email protected] Vulnerability reports: SECURITY.md Client that will not connect, or one missing from the list above: open an issue

Compliance

AlgoVesta does not generate signals, does not hold, receive or move client funds, and does not provide investment advice. Trading carries risk; automation does not remove it. Every new key starts on paper.

License

Copyright © 2026 AlgoVesta. Documentation and configuration examples in this repository are licensed under CC BY 4.0. The AlgoVesta MCP server itself is proprietary and hosted; this repository contains no server source code.