Apify: MCP server, CLI and agent surfaces
Sign-in required, tools not seen, not counted. The MCP endpoint listed for Apify at mcp.apify.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in.
Fact sheet
| Company | Apify |
|---|
| Domain | apify.com |
|---|
| Category | Agent Tools (Ora leaderboard category) |
|---|
| MCP server | Sign-in required (OAuth with client registration) |
|---|
| Ora score | 96, grade A+; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for apify.com, a vendor-published score) |
|---|
| Company found through | the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard |
|---|
| Last verified | 4 November 2026 |
|---|
MCP server
| Endpoint | https://mcp.apify.com |
|---|
| How it was found | listed in the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard |
|---|
| Transport | streamable-http |
|---|
| HTTP status | 401 |
|---|
| Connected | 4 November 2026, 20:02 UTC |
|---|
| Handshake time | 1,494 ms over 1 attempt |
|---|
| Documentation | docs.apify.com |
|---|
The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools.
Connector log
2 connections on 4 November 2026, read-only methods only
- 19:56:29Z https://mcp.apify.com sent initialize result auth-required (HTTP 401) 1524 ms
- 20:02:05Z https://mcp.apify.com sent initialize result auth-required (HTTP 401) 1494 ms
Authentication
| Auth type | OAuth with client registration |
|---|
| What the challenge said | Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token. Pass an Apify API token in the Authorization: Bearer <token> header. Manage tokens at https://console.apify.com/account/integrations" |
|---|
| Protected resource metadata | mcp.apify.com |
|---|
| Authorization server metadata | console-backend.apify.com |
|---|
| Registration endpoint | https://console-backend.apify.com/oauth/apps |
|---|
| Client ID metadata documents | supported |
|---|
| Auth as listed by a registry | API Key (a claim, not checked by connecting) |
|---|
The sign-in route, step by step
- Request
https://mcp.apify.com without a token. It answers 401 and a WWW-Authenticate header. - Read the protected resource metadata at
https://mcp.apify.com/.well-known/oauth-protected-resource to find the authorization server. - Register a client at the registration endpoint
https://console-backend.apify.com/oauth/apps (dynamic client registration), so no human has to create an app first. - Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes.
See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.
CLI
| Package | apify-cli on npm (page) |
|---|
| Exists | yes |
|---|
| Latest version | 1.11.0 |
|---|
| Last publish | 29 October 2026 |
|---|
| Command names | actor, apify, apify-cli |
|---|
| Checked | 4 November 2026 |
|---|
Other agent surfaces
Agent surfaces other than MCP and CLI| Surface | Result |
|---|
| OpenAPI file | Found: apify.com (JSON, via a direct request). |
| WebMCP in the initial HTML | Not detected on the home page by the shared crawl. |
| MCP discovery file | Not found (the crawl got a non-200 answer). |
| A2A agent card | Not found (the crawl got a non-200 answer). |
| A2A agent card (older path) | Not found (the crawl got a non-200 answer). |
| agents.json | Not found (the crawl got a non-200 answer). |
| OAuth authorization server metadata | Found: apify.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. |
| NLWeb endpoint | Not checked in this edition. |
Registry listings
Registry listings| Registry | Listed |
|---|
| Official MCP Registry | Yes: com.apify/apify-mcp-server, io.github.4robot/hexadata, io.github.AndriyVK/apify-document-tools and 2 more |
| GitHub MCP Registry | Yes |
| awesome-remote-mcp-servers | Yes |
| Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. |
| Glama | Not checked: Glama's API needs a key and attribution terms. |