Trade Agent MCP Server

Created By
Trade-Agenta year ago
Guide to connect to Trade Agent's MCP server and trade stocks and crypto
Overview

what is Trade Agent MCP Server?

Trade Agent MCP Server is a platform that facilitates stock and cryptocurrency trading through natural language interaction with various brokerages.

how to use Trade Agent MCP Server?

To use the Trade Agent MCP Server, create an account at the Trade Agent website, sign up for a free trial of the Pro plan, and connect your brokerage account. Then, connect your MCP client to the provided endpoint and authenticate through the OAuth flow.

key features of Trade Agent MCP Server?

  • Create and execute trade orders using natural language.
  • Show account details and linked brokerages.
  • Search for current prices and metadata of stocks and cryptocurrencies.
  • Upcoming features include portfolio queries and market queries.

use cases of Trade Agent MCP Server?

  1. Executing trades on platforms like Robinhood and Coinbase.
  2. Querying portfolio performance and asset prices.
  3. Facilitating copy trading based on other investors' portfolios.

FAQ from Trade Agent MCP Server?

  • Which brokerages are supported?

Currently supports Robinhood, E*TRADE, Coinbase, and Kraken, with more to be added.

  • Do I need to run anything locally?

No, the server is remote-only, requiring no local deployment.

  • How do I connect to the server?

Connect your MCP client to the endpoint and authenticate through the browser-based OAuth flow.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Trade-Agent
Star
3
Language
-
License
CC0-1.0 license
Category
finance
Tags

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago