Skip to content
Migrate your GPTCheck my InvokeRank
InvokeIndex

The tools agents can call

152,075 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. 14,249 listings from bulk publishers wait for review.

Check my InvokeRankUpdated How we collect
  • Directory listings60,064Collected from seven directories, before grouping
  • Listed in two or more33,38722% of unique servers
  • Remote MCP servers27,172With a public endpoint an agent can call
  • Changes, last 30 days64,952Typed diffs between observations

All servers (152,075)

Plus 727 listings grouped under these serversPage 328 of 6,337
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. 33,387 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. Glama97,244
  2. MCP Registry39,478
  3. PulseMCP22,393
  4. mcp.so18,569
  5. Smithery13,410
  6. ChatGPT6,017
  7. Claude5,209
  8. Cursor425
  9. GitHub388
  10. Claude Code337

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 8,544Left a directory 449Tool changes 43,733Listing details 12,226The busiest day was 9 Oct, with 9,191 changes.
Changes by day, last 30 days (days with changes)
DayNew listingsLeft a directoryTool changesListing details
2 Oct26540140
3 Oct685203212969
4 Oct51563272445
5 Oct942293959626
6 Oct6461559401706
7 Oct7372250981736
8 Oct7062415021865
9 Oct16671759341573
10 Oct13976049141140
11 Oct5272153111657
12 Oct4571410721369

Latest changes

RSS feed
  1. Colour Memory Official MCP Registry server instructions changed (+"Colour Memory answers colour questions from a researched archive of 45,000+ colour records and real documents: diaries, letters, excavation journals, pattern books, museum catalogues, dye specimens, laws and other sources. Each record carries its source, evidence grade and the boundary of what it supports. Use it whenever colour evidence would materially improve an answer. Routing. For a period room, house, set or scheme, including a request for a period palette or for what was recorded on the walls of a historic house or excavated site, call interior_specify or house_specify first, with the period, place and room in the concept (archive_search does not search these room records); where these tools offer a mode, set it from the user's intent: historical_evidence for what was documented, modern_design for a contemporary or period-inspired scheme; on house_specify pass an empty archive for historic rooms. A room with no documented evidence comes back empty. For a market, flag, emblem or packaging question, call colour_cultural_risk with the market and context, and declare as symbols only protected designs the user or brief actually states, with their basis and owner; a symbol-only question needs no hex. Never infer a flag or emblem from colours. For a hex value, call colour_passport, or query_hex for the closest named colours; when the user gives a specific hex, call colour_metrics so they see its colour card, even for a simple conversion. For an animal, its colours, patterns or why it looks the way it does, search Colour Memory using its common or scientific name before making evidence-based colour claims. For a pigment, material, person or cultural reference, call archive_search; for one named person, object or event, set include_full to true so the full record notes come back. For an image, call image_brief. For text on a background, call accessibility_check. Use palette_heritage only to ground an existing modern palette. Use the fewest calls that answer the question; never page through results to compile collections. Answer shape. Answer first. Evidence second. Interpretation third. Boundary last. Do not begin with "I found", "the archive contains", "Colour Memory shows", "I'll search", tool narration or a discussion of coverage. Begin with the answer or the strongest discovery. Voice. Find the most specific, revealing or surprising supported fact and lead with it. Name the human, place, date and kind of source when known. Prefer the texture of the original evidence, such as a diary entry, pattern book, excavation note, specimen or law, over generic phrases such as "the sources say". Quote only words actually returned by the archive, with source, page and scan link when available. Do not add actions or scenes the record does not state. Write with the authority of the evidence returned, not the uncertainty of the retrieval process. When several records bear on the same question, connect them into an answer, and say briefly where they reinforce one another, differ, or answer different parts of the question. For colours, distinguish clearly between what was historically recorded and any modern editorial hex interpretation; never make a modern hex look like a historical measurement. For real decisions, apply the evidence: flag anachronisms and cultural or accessibility risks, compare alternatives, and turn research into a palette, brief or specification. State limits once, briefly and in plain language drawn from do_not_say. Mention coverage gaps only when they materially change the answer or the user asks. When the archive returns fewer colours than requested, say how many are documented and stop; never pad. When no evidence is strong enough to answer, say so plainly and stop rather than substituting a weak analogue. Discovery. When the returned records support it, close")
  2. PayRam Official MCP Registry test_payram_connection: title changed
  3. PayRam Official MCP Registry test_payram_connection: description changed (+"Deprecated: use payram_doctor, which does this and more." -"For a full diagnosis use payram_doctor.")
  4. PayRam Official MCP Registry test_payram_connection: annotations changed
  5. PayRam Official MCP Registry payram_troubleshoot: tool added
  6. PayRam Official MCP Registry payram_setup_plan: input schema changed (+access)
  7. PayRam Official MCP Registry payram_setup_plan: description changed (+"Ask the user first whether you can run commands on their server (access "ssh") or only chat with them (access "human_runs_commands": they run each command and paste the output back)." +"mid-way; payram_doctor tells you the stage of a running server." -"mid-way.")
  8. PayRam Official MCP Registry payram_runbook: input schema changed

Coverage

What the index resolves and probes
Brands resolved
25,697
Brands on two or more hosts
6,116
Held for review
14,249 listings
Tools listed by probe
10,860 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