explaingit

mphinance/awesome-broker-mcp

Analysis updated 2026-05-18

0JavaScriptAudience · developerLicense

TLDR

A verified directory checking which stock and crypto brokers actually let an AI place trades through MCP, and which don't.

Mindmap

mindmap
  root((Broker MCP))
    What it does
      Verified broker directory
      Trade capability check
      Official vs community
    Tech stack
      JavaScript
      Markdown
      MCP protocol
    Use cases
      Broker research
      Safety posture check
      Paper trading discovery
    Audience
      AI agent developers
      Traders

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Check whether a specific broker has a working MCP server before connecting an AI assistant to it.

USE CASE 2

Compare which broker integrations can place live trades versus only draft orders or read data.

USE CASE 3

Find a broker with paper trading enabled by default to test an AI trading setup safely.

USE CASE 4

Avoid the trap of assuming a broker supports MCP just because its docs mention it.

What is it built with?

JavaScriptMarkdownMCP

How does it compare?

mphinance/awesome-broker-mcp00kaku/gallery-slider-block3rd-eden/ircb.io
Stars0
LanguageJavaScriptJavaScriptJavaScript
Last pushed2021-05-192016-11-16
MaintenanceDormantDormant
Setup difficultyeasyeasy
Complexity2/52/5
Audiencedevelopergeneraldeveloper

Figures from each repo's GitHub metadata at analysis time.

In plain English

Awesome Broker MCP is a curated directory that answers one specific question: which stock and crypto brokers actually let an AI assistant place a trade through MCP, the protocol that lets an AI connect to outside tools. It checks 65 brokers directly against their own documentation or their own server code, rather than copying from other lists, and it lists brokers with no working solution at all just as clearly as ones that work well. Each broker gets marked with a simple set of symbols showing whether its integration can actually place a real order on its own, only draft an order for a human to submit, only read account data with no trading ability, or has no MCP route at all after being checked. The list separates official integrations built by the broker itself from unofficial community-built servers, and from aggregator services that offer no direct connection but route through a shared platform instead. A second review pass went back over the whole list specifically trying to find mistakes in the first pass, and found that eleven of the original nineteen entries needed a correction, with each fix documented on the page rather than silently changed. The README recommends specific starting points depending on what someone wants: a broker whose server architecturally cannot submit a live order for the safest option, brokers with sandbox or paper trading modes turned on by default for practice without real money, and read-only aggregator services for people who only want analysis rather than execution. It calls out three common traps: that being official or community-built has nothing to do with whether a server runs locally or remotely, that a project claiming MCP support in its documentation does not always mean it actually registers a trading tool, and that safe default settings like paper trading are not universal, since at least one broker has no paper mode at all. The project is a documentation and comparison repository rather than something you install or run, built for anyone considering connecting an AI assistant to a real brokerage account. It is released under the CC0-1.0 license, which places it in the public domain.

Copy-paste prompts

Prompt 1
Which brokers in this list can actually place a live trade through their MCP server?
Prompt 2
Explain the difference between draft-only, read-only, and trading MCP servers in this directory.
Prompt 3
Show me which official broker integrations default to paper or sandbox trading.
Prompt 4
Help me understand what the second review pass corrected and why those entries were wrong.

Frequently asked questions

What is awesome-broker-mcp?

A verified directory checking which stock and crypto brokers actually let an AI place trades through MCP, and which don't.

What language is awesome-broker-mcp written in?

Mainly JavaScript. The stack also includes JavaScript, Markdown, MCP.

Who is awesome-broker-mcp for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.