Skip to content
Migrate your GPTCheck my InvokeRank
InvokeIndex

The tools agents can call

167,838 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,086 listings from bulk publishers wait for review.

Check my InvokeRankUpdated How we collect
  • Directory listings73,777Collected from seven directories, before grouping
  • Listed in two or more36,63322% of unique servers
  • Remote MCP servers33,776With a public endpoint an agent can call
  • Changes, last 30 days182,462Typed diffs between observations

Glama (102,306)

Plus 334 listings grouped under these serversPage 644 of 4,263
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

78%of servers are listed in one directory only. 36,633 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,306
  2. MCP Registry47,422
  3. PulseMCP22,400
  4. mcp.so19,383
  5. Smithery14,474
  6. ChatGPT8,790
  7. Claude7,369
  8. GitHub596
  9. Claude Code520
  10. Cursor475

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 22,782Left a directory 899Tool changes 131,044Listing details 27,737The busiest day was 15 Oct, with 10,748 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 Oct7042415021864
9 Oct16671759321572
10 Oct13976049091137
11 Oct5272150281634
12 Oct7532044771770
13 Oct871215291627
14 Oct853284194665
15 Oct1276208675777
16 Oct11111038540842
17 Oct1066175225830
18 Oct669216954725
19 Oct1841926805986
20 Oct875134874756
21 Oct1153857641369
22 Oct9441857741895
23 Oct11843870261864
24 Oct11081971792069
25 Oct7021159921317
26 Oct330351986476

Latest changes

RSS feed
  1. arifOS — Constitutional AI Governance Official MCP Registry arif_seal: input schema changed
  2. arifOS — Constitutional AI Governance Official MCP Registry arif_route: description changed (+"prepares a dispatch envelope for" +"and target" +"contract. Calling")
  3. AstraNL Official MCP Registry order_materials: annotations changed
  4. AstraNL Official MCP Registry ground_component: description changed (+"Writes (why the tool is not read-only): each fresh answer, not one served from the 24 hour cache, appends one event to the public AstraLock log with the part number, the maker, the digest, the availability and the number of exact offers, so the answer can be verified later, and stores the answer in an AstraNL database table (component_groundings) that serves the cache and counts the budget; the row names only the door (mcp), nothing about the caller. Live budget: 40 fresh reads a day across all MCP callers; after that only cached answers, status DAILY_LIVE_BUDGET_SPENT. Logging: every MCP call is journaled with the tool name, outcome, argument length, caller class (external, probe, crawler, self), a SHA-256 hash of the caller network /24 and the client family; for demand statistics also the first 160 characters of a query, question, title or id argument and the user-agent; never the address itself, other arguments or an account." -"read-only")
  5. AstraNL Official MCP Registry ground_component: annotations changed
  6. AstraNL Official MCP Registry ground_citation: description changed (+"Writes (why the tool is not read-only): each fresh answer, not one served from the 24 hour cache, appends one event to the public AstraLock log with the DOI, the digest and the status, so the answer can be verified later, and stores the answer in an AstraNL database table (citation_groundings) that serves the cache and counts the budget; the row names only the door (mcp), nothing about the caller. Live budget: 300 fresh reads a day across all MCP callers; after that only cached answers, status DAILY_LIVE_BUDGET_SPENT. Logging: every MCP call is journaled with the tool name, outcome, argument length, caller class (external, probe, crawler, self), a SHA-256 hash of the caller network /24 and the client family; for demand statistics also the first 160 characters of a query, question, title or id argument and the user-agent; never the address itself, other arguments or an account." -"read-only")
  7. AstraNL Official MCP Registry ground_citation: annotations changed
  8. AstraNL Official MCP Registry fetch: description changed (-"id 'context' returns the AstraNL continuation packet: live state, open mandates and recent sessions, the same text as https://astranl.com/api/context.md.")

Coverage

What the index resolves and probes
Brands resolved
32,990
Brands on two or more hosts
7,874
Held for review
15,086 listings
Tools listed by probe
13,799 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