MatrixRecord of · MCP Authorization 2026-07-28

Apify

How it meets the 23 requirements of MCP Authorization.

Supported
12
Unsupported
2
Unknown, recorded
0
Not observed yet
9
Endpoint
https://mcp.apify.com
Transport
Streamable HTTP
Access
Public Anyone can connect; where an account is needed, anyone can create one by self-service sign-up. Manual check · jbspeakr (documentation pass with Claude Code) · · evidence · An Apify account, created by self-service sign-up, is the only prerequisite; some tools work without one.
Auth
OAuth An OAuth 2.x authorization obtained through the server's authorization server. Manual check · jbspeakr (documentation pass with Claude Code) · · evidence · The recommended hosted connection is Streamable HTTP with OAuth sign-in; an Apify API token as bearer header is the alternative.
Why it is listed
Listed because it appears in a public directory of MCP servers. Source
Homepage
https://apify.com
Notes
The directory labels this server API Key; Apify's docs now recommend OAuth, so the atlas records OAuth.

Against MCP Authorization 2026-07-28current

  • Supported 12
  • Unsupported 2
  • Unknown 9

Passive scan · Requests

  • MUST8 supported
  • SHOULD3 supported, 1 unsupported
  • MAY2 supported

Contribute a correctionWithdraw this serverJSON

Older revisions of the matrix: 2025-11-25

MCP server features 13

FeatureLevelStatusObservedEvidence
Protected Resource Metadata servedmcp.prm · Discovery · Authorization Server Discovery › Authorization Server LocationMUSTSupportedPassive scan · scanner@0.4.0source— HTTP 200; resource: https://mcp.apify.com
PRM lists an authorization servermcp.prm.authorization-servers · Discovery · Authorization Server Discovery › Authorization Server LocationMUSTSupportedPassive scan · scanner@0.4.0source— HTTP 200; authorization_servers: [https://console-backend.apify.com]
PRM lists scopes_supportedmcp.prm.scopes-supported · Discovery · Authorization › Scope Selection StrategyMAYSupportedPassive scan · scanner@0.4.0source— HTTP 200; scopes_supported: [full_api_access]
PRM reachable at a well-known URImcp.prm.well-known · Discovery · Authorization Server Discovery › Protected Resource Metadata Discovery RequirementsMUSTSupportedPassive scan · scanner@0.4.0source— HTTP 200; found at the root location
resource_metadata in the 401 challengemcp.prm.www-authenticate · Discovery · Authorization Server Discovery › Protected Resource Metadata Discovery RequirementsMUSTUnsupportedPassive scan · scanner@0.4.0source— HTTP 401; WWW-Authenticate: absent, no resource_metadata parameter
403 insufficient_scope for step-upmcp.rs.insufficient-scope · Authorization · Authorization › Scope Challenge HandlingSHOULDUnknown no observationno observation yet
Scope in the WWW-Authenticate challengemcp.rs.scope-challenge · Authorization · Authorization › Scope Selection StrategySHOULDUnsupportedPassive scan · scanner@0.4.0source— HTTP 401; WWW-Authenticate: absent, no scope parameter
No offline_access in advertised scopesmcp.prm.no-offline-access · Tokens · Authorization › Refresh TokensSHOULDSupportedPassive scan · scanner@0.4.0source— HTTP 200; scopes_supported without offline_access: [full_api_access]
401 for missing or invalid tokensmcp.rs.401-on-invalid · Tokens · Authorization › Token HandlingMUSTUnknown no observationno observation yet
Audience validationmcp.rs.audience-validation · Tokens · Security Considerations › Access Token Privilege RestrictionMUSTUnknown no observationno observation yet
Bearer token only in the Authorization headermcp.rs.bearer-header · Tokens · Authorization › Access Token UsageMUSTUnknown no observationno observation yet
No token passthrough to upstream APIsmcp.rs.no-passthrough · Delegation · Security Considerations › Access Token Privilege RestrictionMUSTUnknown no observationno observation yet
Per-client consent on proxy serversmcp.proxy.consent · Consent · Security Considerations › Confused Deputy ProblemMUSTUnknown no observationno observation yet

Authorization server features 10

FeatureLevelStatusObservedEvidence
Metadata issuer matches the discovery URLmcp.as.issuer-match · Discovery · Authorization Server Discovery › Authorization Server Metadata DiscoveryMUSTSupportedPassive scan · scanner@0.4.0source— HTTP 200; issuer: https://console-backend.apify.com equals the issuer the PRM named
Authorization server metadata discoverablemcp.as.metadata · Discovery · Authorization Server Discovery › Authorization Server Metadata DiscoveryMUSTSupportedPassive scan · scanner@0.4.0source— HTTP 200; issuer: https://console-backend.apify.com
Client ID Metadata Documents supportedmcp.as.cimd · Registration · Client Registration › Client ID Metadata DocumentsSHOULDSupportedPassive scan · scanner@0.4.0source— HTTP 200; client_id_metadata_document_supported: true
Dynamic Client Registration offeredmcp.as.dcr · Registration · Client Registration › Dynamic Client RegistrationMAYSupportedPassive scan · scanner@0.4.0source— HTTP 200; registration_endpoint: https://console-backend.apify.com/oauth/apps
Documented pre-registration pathmcp.as.preregistration · Registration · Client Registration › Pre-registrationSHOULDUnknown no observationno observation yet
Issuer identifier in authorization responsesmcp.as.iss-param · Authorization · Authorization › Authorization Response ValidationSHOULDSupportedPassive scan · scanner@0.4.0source— HTTP 200; authorization_response_iss_parameter_supported: true
PKCE with S256 advertisedmcp.as.pkce-s256 · Authorization · Security Considerations › Authorization Code ProtectionMUSTSupportedPassive scan · scanner@0.4.0source— HTTP 200; code_challenge_methods_supported: [S256]
Refresh token rotation for public clientsmcp.as.refresh-rotation · Tokens · Security Considerations › Token TheftMUSTUnknown no observationno observation yet
Resource indicators honouredmcp.as.resource-indicator · Tokens · Security Considerations › Token Audience Binding and ValidationMUSTUnknown no observationno observation yet
All endpoints served over HTTPSmcp.as.https · Transport · Security Considerations › Communication SecurityMUSTSupportedPassive scan · scanner@0.4.0source— HTTP 200; all 6 endpoints use https

This server's ledger

No status change on record

Every cell of this server still shows the status of its first observation.

The whole ledger

What the scanner asked

The requests behind the rows marked passive scan above, in the order the scanner makes them, each with the newest answer recorded. None carries a credential or a message.

  1. GEThttps://mcp.apify.com/.well-known/oauth-protected-resourceHTTP 200read resource, authorization_servers, scopes_supported
  2. GEThttps://mcp.apify.com/HTTP 401read status, WWW-Authenticate
  3. GEThttps://console-backend.apify.com/.well-known/oauth-authorization-serverHTTP 200read issuer, client_id_metadata_document_supported, registration_endpoint, authorization_response_iss_parameter_supported, code_challenge_methods_supported
  4. 14 checks, read into the tables above

resource_metadata in the 401 challenge counts as supported because PRM reachable at a well-known URI is supported; the specification asks for one of the two.

Newest scanner observation · letsauth-scanner/0.4.0 · reproduce with pnpm scan apify · scan JSON · data file · how the scanner works