Apify

The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established on 2026-09-07 and the MCP URL has not been probed live yet.

mcp_status, verbatim from the file:

official

mcp_url, verbatim from the file:

https://mcp.apify.com (docs: https://docs.apify.com/platform/integrations/mcp; registry name com.apify/apify-mcp-server)

• https://mcp.apify.com
• https://docs.apify.com/platform/integrations/mcp

A tool below is one the server NAMES. Nobody has called it. That is the same two tier honesty rule the rest of the directory runs on: a named tool is research, and BENCH-TESTED stays the only claim that anybody ran anything.

• abort-actor-run
  runs
  evidence: in a README table · calling it reads
• build-actor
  builds
  evidence: in a README table · calling it reads
• call-actor
  actors
  evidence: in a README table · calling it reads
• create-actor-task
  tasks
  evidence: in a README table · calling it writes
• create-schedule
  schedules
  evidence: in a README table · calling it writes
• delete-schedule
  schedules
  evidence: in a README table · calling it writes
• fetch-actor-details
  actors
  evidence: in a README table · calling it reads
• fetch-apify-docs
  docs
  evidence: in a README table · calling it reads
• get-actor-build
  builds
  evidence: in a README table · calling it reads
• get-actor-build-log
  builds
  evidence: in a README table · calling it reads
• get-actor-run
  runs
  evidence: in a README table · calling it reads
• get-actor-run-list
  runs
  evidence: in a README table · calling it reads
• get-actor-run-log
  runs
  evidence: in a README table · calling it reads
• get-actor-task
  tasks
  evidence: in a README table · calling it reads
• get-dataset
  storage
  evidence: in a README table · calling it reads
• get-dataset-items
  storage
  evidence: in a README table · calling it reads
• get-dataset-list
  storage
  evidence: in a README table · calling it reads
• get-dataset-schema
  storage
  evidence: in a README table · calling it reads
• get-key-value-store
  storage
  evidence: in a README table · calling it reads
• get-key-value-store-keys
  storage
  evidence: in a README table · calling it reads
• get-key-value-store-list
  storage
  evidence: in a README table · calling it reads
• get-key-value-store-record
  storage
  evidence: in a README table · calling it reads
• get-schedule
  schedules
  evidence: in a README table · calling it writes
• publish-actor-task
  tasks
  evidence: in a README table · calling it reads
• report-problem
  dev
  evidence: in a README table · calling it reads
• search-actors
  actors
  evidence: in a README table · calling it reads
• search-apify-docs
  docs
  evidence: in a README table · calling it reads
• unpublish-actor-task
  tasks
  evidence: in a README table · calling it reads
• update-actor-task
  tasks
  evidence: in a README table · calling it writes
• update-schedule
  schedules
  evidence: in a README table · calling it writes

141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. Every name across every server is on the tools index.

Install, as the source shows it:

brew install apify-cli

quoted from https://formulae.brew.sh/formula/apify-cli on 2026-09-27, via brew

Packages seen, with the version on 2026-09-27:

• brew: apify-cli 1.10.0

A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it. Harvest date 2026-09-27.

api_gate, verbatim from the file:

free - the pricing page lists Free at $0/month with "$5" of monthly prepaid platform usage and "No credit card is required", then Starter $19/month, Scale $199/month and Business $999/month. The Free plan "lets you use most of the features of the Apify platform, but with certain limits" (5 concurrent runs, rented Actors on trial only).

No documentation URL recorded.

727 of 1252 entries are in the same position. Blank is legal and it is published as blank.

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health:

• https://github.com/apify/apify-mcp-server

github.com/apify tied to the vendor by rule 3, account website https://apify.com/ has the vendor's domain, confidence strong

The five most recently pushed, on 2026-09-08:

Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.

No job tag on this entry.

981 of 1,252 entries are untagged. An empty list here means nobody has tagged this, not that the tool does nothing. The vocabulary is closed, so a tool whose job is genuinely not in it stays blank rather than being forced into the nearest tag.

• https://docs.apify.com/platform/integrations/mcp
• https://apify.com/pricing
• https://mcp.apify.com
• https://github.com/apify/apify-mcp-server

4 source URLs. Raw sources field, verbatim:

https://docs.apify.com/platform/integrations/mcp, https://apify.com/pricing, https://mcp.apify.com, https://github.com/apify/apify-mcp-server

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.