Skip to content
Migrate your GPTCheck my InvokeRank
InvokeIndex

The tools agents can call

172,701 unique MCP servers across ten major directories and registries, each with its sources and history.

Each server counts once, however many directories list it. Glama, PulseMCP and mcp.so listings arrive through MCP Toplist’s open dataset, used under CC BY 4.0. 15,387 listings from bulk publishers wait for review.

Check my InvokeRankUpdated How we collect
  • Directory listings76,165Collected from seven directories, before grouping
  • Listed in two or more36,75421% of unique servers
  • Remote MCP servers35,732With a public endpoint an agent can call
  • Changes, last 30 days218,300Typed diffs between observations

Official MCP Registry (50,150)

Plus 929 listings grouped under these serversPage 878 of 2,090
Inside the index

Where the servers are listed

Each directory is a shelf. See how many shelves each server sits on, how large each shelf is, and what moved this month.

Updated

How many shelves

Servers by the number of directories listing them

79%of servers are listed in one directory only. 36,754 are listed in two or more.

Directories listing the server. Copies grouped under a server are not counted again.

The shelves

Unique servers listed in each directory
  1. Glama102,566
  2. MCP Registry50,150
  3. PulseMCP22,358
  4. mcp.so19,427
  5. Smithery16,466
  6. ChatGPT8,790
  7. Claude7,399
  8. GitHub639
  9. Claude Code479
  10. Cursor476

Collected by us Via MCP Toplist’s dataset

A server listed in several directories counts once in each. Pick a shelf to browse it.

What changed

Typed diffs between observations, last 30 days
New listings 25,246Left a directory 960Tool changes 158,308Listing details 33,786The busiest day was 15 Oct, with 10,738 changes.
Changes by day, last 30 days (days with changes)
DayNew listingsLeft a directoryTool changesListing details
2 Oct26540140
3 Oct647203212969
4 Oct51463265441
5 Oct942293912615
6 Oct6461559201698
7 Oct7372250891699
8 Oct7032415021864
9 Oct16671759321572
10 Oct13976049091137
11 Oct5272150281634
12 Oct7532044771770
13 Oct871215291627
14 Oct853284194665
15 Oct1266208675777
16 Oct11111038540842
17 Oct1066175225830
18 Oct669216954725
19 Oct1841926805986
20 Oct875134874756
21 Oct1137857641369
22 Oct9431857741881
23 Oct11843870261864
24 Oct11081971792069
25 Oct7021159921317
26 Oct7304363251697
27 Oct7192867871947
28 Oct6661469711980
29 Oct56588288754
30 Oct1423879161

Latest changes

RSS feed
  1. AnchoredIP Official MCP Registry server instructions changed (+"Then prove it from the machine with the verify_command create_tunnel returns: it prints the address we saw the request arrive from, and from then on lease_status reports the egress as verified.")
  2. Autoview Official MCP Registry sandbox_run: description changed
  3. Autoview Official MCP Registry sandbox_results: description changed (+"more, next_step" +"next_step = { market, practice_venue, practice_venue_name, same_venue, free, connect_url, text } names the free testnet or demo venue for the newest order's market and the page where your user connects it; practice_venue is null when Autoview has no match, and free is false when the only demo is not free to open. Pass text to your user as the next step." +"Fill model (every fill carries it as fill_model): each order fills at one snapshot price taken when the alert arrives, either the venue's public ticker (its best ask for a buy and best bid for a sell when the venue gives them, otherwise its last trade) or a price you supply (price, or fp= in the alert). A market order fills at that price. A marketable limit (a buy limit at or above it, a sell limit at or below it) fills at that price, never at the limit; any other limit stays open as not_filled and never fills later. The sandbox does not model order-book depth, slippage, latency or partial fills, and a caller price or last trade carries no spread, so live results will differ. For live-like execution, use the venue's own testnet or demo account through Autoview (pricing lists them with demo: true, at $0).")
  4. Autoview Official MCP Registry live_limits: tool added
  5. Autoview Official MCP Registry entry: description changed (+"Live limits: a live:true order (not cancel/close/flat) must fit this token's user-set caps AND, once your user has set them, the account caps (they cover every agent token on the account together; with none set, the token's caps alone apply), read them with `live_limits`. It must be a limit order with price and a plain number quantity, in a USD or USD-stablecoin quoted market; quantity x limit price (USD) must be at most the token's max order size (and the account's, if set), and today's totals (UTC day, counted at dispatch; per token, and for the whole account if an account daily limit is set) at most those daily limits. Refusal codes, each with fix steps: agent_trading_paused (your user paused all agent trading on the account; cancel/close/flat still work), caps_not_set, caps_unavailable, cap_max_order_exceeded, cap_account_max_order_exceeded, cap_daily_limit_exceeded, cap_account_daily_limit_exceeded, cap_limit_price_required, cap_quantity_unsupported, cap_quote_unsupported, cap_market_unsupported. Only your user can set or raise the caps, or pause and resume agent trading, at /account/tokens/.")
  6. Autoview Official MCP Registry server instructions changed (+"https://autoview.com/account/tokens/?src=mcp&tool=instructions)," +"A live entry order must also fit the token's live limits (max order size and daily limit in USD) and, once the user sets them, the account's (they cover all agent tokens together), which only the user sets on the website; call live_limits to read them and tell your user. The user can also pause all agent trading on the account; while paused, every new live entry order is refused agent_trading_paused, and cancel/close/flat still work. No tool can turn the pause on or off." -"/account/tokens/),")
  7. Base Transaction Decoder Official MCP Registry explain_transaction: description changed (+"account_delegated (EIP-7702: the transaction hands control of an account to a contract),")
  8. Bitmovin Observability MCP Official MCP Registry getImpressionOverview: description changed (+"The facts of" +"an impressionId, together with the findings evaluated over them. Facts cover the session context" +"player, stream, CDN),")

Coverage

What the index resolves and probes
Brands resolved
34,477
Brands on two or more hosts
7,992
Held for review
15,387 listings
Tools listed by probe
14,618 servers

Where are you listed?

Paste your MCP server, plugin or company URL to see your listings, tools and scan findings in one place.

Check my InvokeRank Scan a server