MatrixRecord of · MCP Authorization 2026-07-28

Calendly

How it meets the 23 requirements of MCP Authorization.

Supported
10
Unsupported
4
Unknown, recorded
0
Not observed yet
9
Endpoint
https://mcp.calendly.com
Transport
Streamable HTTP
Access
Unknown nobody has stated this yet
Auth
OAuth An OAuth 2.x authorization obtained through the server's authorization server. Manual check · jbspeakr (documentation pass with Claude Code) · · evidence · OAuth 2.1 authorization code with PKCE (S256), dynamic client registration (RFC 7591) and discovery through protected resource metadata; personal access tokens and pre-registered client IDs are not supported.
Why it is listed
Listed because it appears in a public directory of MCP servers. Source
Homepage
https://calendly.com

Against MCP Authorization 2026-07-28current

  • Supported 10
  • Unsupported 4
  • Unknown 9

Passive scan · Requests

  • MUST8 supported
  • SHOULD1 supported, 3 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.calendly.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://calendly.com/]
PRM lists scopes_supportedmcp.prm.scopes-supported · Discovery · Authorization › Scope Selection StrategyMAYSupportedPassive scan · scanner@0.4.0source— HTTP 200; scopes_supported: [mcp:notetaker:read, mcp:scheduling:read, mcp:scheduling:write]
PRM reachable at a well-known URImcp.prm.well-known · Discovery · Authorization Server Discovery › Protected Resource Metadata Discovery RequirementsMUSTUnsupportedPassive scan · scanner@0.4.0source— HTTP 200; not at either well-known location (root HTTP 200, root HTTP 200)
resource_metadata in the 401 challengemcp.prm.www-authenticate · Discovery · Authorization Server Discovery › Protected Resource Metadata Discovery RequirementsMUSTSupportedPassive scan · scanner@0.4.0source— HTTP 401; WWW-Authenticate resource_metadata: https://mcp.calendly.com/.well-known/oauth-protected-resource
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: Bearer resource_metadata="https://mcp.calendly.com/.well-known/oauth-protected-resource", 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: [mcp:notetaker:read, mcp:scheduling:read, mcp:scheduling:write]
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://calendly.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://calendly.com/
Client ID Metadata Documents supportedmcp.as.cimd · Registration · Client Registration › Client ID Metadata DocumentsSHOULDUnsupportedPassive scan · scanner@0.4.0source— HTTP 200; client_id_metadata_document_supported: absent
Dynamic Client Registration offeredmcp.as.dcr · Registration · Client Registration › Dynamic Client RegistrationMAYSupportedPassive scan · scanner@0.4.0source— HTTP 200; registration_endpoint: https://calendly.com/oauth/register
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 ValidationSHOULDUnsupportedPassive scan · scanner@0.4.0source— HTTP 200; authorization_response_iss_parameter_supported: absent
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 3 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.calendly.com/.well-known/oauth-protected-resourceHTTP 200read resource, authorization_servers, scopes_supported
  2. GEThttps://mcp.calendly.com/HTTP 401read status, WWW-Authenticate
  3. GEThttps://calendly.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

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

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