Skip to content
Migrate your GPTCheck my InvokeRank
InvokeIndex

The tools agents can call

154,455 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,312 listings from bulk publishers wait for review.

Check my InvokeRankUpdated How we collect
  • Directory listings62,863Collected from seven directories, before grouping
  • Listed in two or more33,70622% of unique servers
  • Remote MCP servers28,541With a public endpoint an agent can call
  • Changes, last 30 days86,102Typed diffs between observations

Official MCP Registry (41,063)

Plus 554 listings grouped under these serversPage 518 of 1,711
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,706 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 Registry41,063
  3. PulseMCP22,397
  4. mcp.so18,602
  5. Smithery13,422
  6. ChatGPT6,541
  7. Claude5,831
  8. Cursor448
  9. GitHub420
  10. Claude Code336

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 11,425Left a directory 515Tool changes 59,894Listing details 14,268The 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 Oct7532044771770
13 Oct871215299629
14 Oct853284199666
15 Oct861113258346

Latest changes

RSS feed
  1. Magic Hour Official MCP Registry video_to_video_create_video: description changed (+"MCP guidance: - Starts an async video job; returns `id` and `credits_charged`. For finished results, call `wait_for_video_project` with that id or poll `GET /v1/video-projects/{id}` until `complete`, `error`, or `canceled`. Results include `downloads`; wait helpers add `exact_download_urls`. Preserve signed URLs and query parameters; never append expiration metadata. - For `*_file_path`, use an existing Magic Hour path or the upload-URL endpoint's `file_path` after uploading raw bytes to its presigned URL. Direct public media URLs may work if stable and fetchable as raw bytes; hotlinked URLs can fail. Prefer the upload-URL endpoint when unsure." -"MCP guidance: - This starts an async video generation job and returns `id` plus `credits_charged` immediately. If the user wants the finished result, call the `wait_for_video_project` helper with the returned id, or poll the matching `GET /v1/video-projects/{id}` endpoint until status is `complete`, `error`, or `canceled`. Completed projects include `downloads` with direct URLs. The custom wait helper also returns `exact_download_urls` separately from expiration metadata. - For `*_file_path` values, prefer an existing Magic Hour file path or a `file_path` returned by the upload-URL endpoint after the file bytes are uploaded. Direct public media URLs may work when they are stable, fetchable, and return raw file bytes, but hotlinked URLs can fail; when in doubt, use the presigned upload flow first and pass the returned `file_path`.")
  2. Magic Hour Official MCP Registry video_projects_retrieve_details: description changed (+"Check the progress of a video project. The `downloads` field is populated after a successful render. **Statuses** - `queued` — waiting to start - `rendering` — in progress - `complete` — ready; see `downloads` - `error` — a failure occurred (see `error`) - `canceled` — user canceled - `draft` — not used" -"Check the progress of a video project. The `downloads` field is populated after a successful render. **Statuses** - `queued` — waiting to start - `rendering` — in progress - `complete` — ready; see `downloads` - `error` — a failure occurred (see `error`) - `canceled` — user canceled - `draft` — not used")
  3. Magic Hour Official MCP Registry video_assets_generate_presigned_url: description changed (+"MCP guidance: - This only creates presigned upload URLs. For local files, upload the raw bytes to each returned `upload_url` outside the generation call, then pass the matching `file_path` into the create tool. - For `*_file_path`, use an existing Magic Hour path or the upload-URL endpoint's `file_path` after uploading raw bytes to its presigned URL. Direct public media URLs may work if stable and fetchable as raw bytes; hotlinked URLs can fail. Prefer the upload-URL endpoint when unsure." -"MCP guidance: - This only creates presigned upload URLs. For local files, upload the raw bytes to each returned `upload_url` outside the generation call, then pass the matching `file_path` into the create tool. - For `*_file_path` values, prefer an existing Magic Hour file path or a `file_path` returned by the upload-URL endpoint after the file bytes are uploaded. Direct public media URLs may work when they are stable, fetchable, and return raw file bytes, but hotlinked URLs can fail; when in doubt, use the presigned upload flow first and pass the returned `file_path`.")
  4. Magic Hour Official MCP Registry text_to_video_create_video: description changed (+"MCP guidance: - Starts an async video job; returns `id` and `credits_charged`. For finished results, call `wait_for_video_project` with that id or poll `GET /v1/video-projects/{id}` until `complete`, `error`, or `canceled`. Results include `downloads`; wait helpers add `exact_download_urls`. Preserve signed URLs and query parameters; never append expiration metadata." -"MCP guidance: - This starts an async video generation job and returns `id` plus `credits_charged` immediately. If the user wants the finished result, call the `wait_for_video_project` helper with the returned id, or poll the matching `GET /v1/video-projects/{id}` endpoint until status is `complete`, `error`, or `canceled`. Completed projects include `downloads` with direct URLs. The custom wait helper also returns `exact_download_urls` separately from expiration metadata.")
  5. Magic Hour Official MCP Registry photo_colorizer_create_image: description changed (+"Starts" +"job;" +"and `credits_charged`. For")
  6. Magic Hour Official MCP Registry lip_sync_create_video: description changed (+"Use only with the user's own likeness or content they are authorized to use. Do not use for impersonation, deception, sexual content, or content involving minors. MCP guidance: - Starts an async video job; returns `id` and `credits_charged`. For finished results, call `wait_for_video_project` with that id or poll `GET /v1/video-projects/{id}` until `complete`, `error`, or `canceled`. Results include `downloads`; wait helpers add `exact_download_urls`. Preserve signed URLs and query parameters; never append expiration metadata. - For `*_file_path`, use an existing Magic Hour path or the upload-URL endpoint's `file_path` after uploading raw bytes to its presigned URL. Direct public media URLs may work if stable and fetchable as raw bytes; hotlinked URLs can fail. Prefer the upload-URL endpoint when unsure." -"MCP guidance: - This starts an async video generation job and returns `id` plus `credits_charged` immediately. If the user wants the finished result, call the `wait_for_video_project` helper with the returned id, or poll the matching `GET /v1/video-projects/{id}` endpoint until status is `complete`, `error`, or `canceled`. Completed projects include `downloads` with direct URLs. The custom wait helper also returns `exact_download_urls` separately from expiration metadata. - For `*_file_path` values, prefer an existing Magic Hour file path or a `file_path` returned by the upload-URL endpoint after the file bytes are uploaded. Direct public media URLs may work when they are stable, fetchable, and return raw file bytes, but hotlinked URLs can fail; when in doubt, use the presigned upload flow first and pass the returned `file_path`. Use only with the user's own likeness or content they are authorized to use. Do not use for impersonation, deception, sexual content, or content involving minors.")
  7. Magic Hour Official MCP Registry image_to_video_create_video: description changed (+"MCP guidance: - Starts an async video job; returns `id` and `credits_charged`. For finished results, call `wait_for_video_project` with that id or poll `GET /v1/video-projects/{id}` until `complete`, `error`, or `canceled`. Results include `downloads`; wait helpers add `exact_download_urls`. Preserve signed URLs and query parameters; never append expiration metadata. - For `*_file_path`, use an existing Magic Hour path or the upload-URL endpoint's `file_path` after uploading raw bytes to its presigned URL. Direct public media URLs may work if stable and fetchable as raw bytes; hotlinked URLs can fail. Prefer the upload-URL endpoint when unsure." -"MCP guidance: - This starts an async video generation job and returns `id` plus `credits_charged` immediately. If the user wants the finished result, call the `wait_for_video_project` helper with the returned id, or poll the matching `GET /v1/video-projects/{id}` endpoint until status is `complete`, `error`, or `canceled`. Completed projects include `downloads` with direct URLs. The custom wait helper also returns `exact_download_urls` separately from expiration metadata. - For `*_file_path` values, prefer an existing Magic Hour file path or a `file_path` returned by the upload-URL endpoint after the file bytes are uploaded. Direct public media URLs may work when they are stable, fetchable, and return raw file bytes, but hotlinked URLs can fail; when in doubt, use the presigned upload flow first and pass the returned `file_path`.")
  8. Magic Hour Official MCP Registry image_projects_retrieve_details: description changed (+"Check the progress of a image project. The `downloads` field is populated after a successful render. **Statuses** - `queued` — waiting to start - `rendering` — in progress - `complete` — ready; see `downloads` - `error` — a failure occurred (see `error`) - `canceled` — user canceled - `draft` — not used" -"Check the progress of a image project. The `downloads` field is populated after a successful render. **Statuses** - `queued` — waiting to start - `rendering` — in progress - `complete` — ready; see `downloads` - `error` — a failure occurred (see `error`) - `canceled` — user canceled - `draft` — not used")

Coverage

What the index resolves and probes
Brands resolved
27,401
Brands on two or more hosts
6,441
Held for review
14,312 listings
Tools listed by probe
11,544 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