DialMCP · OAuth Scopes
DialMCP OAuth Scopes
OAuth 2.0
none
DialMCP uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.
This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.
CompanyMCPAI AgentsPhone CallsVoice AITelephony
Scopes: 0
Flows:
Method: none
Scopes (0)
DialMCP implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.
The docs state "DialMCP does not use OAuth scopes. The metadata has no scopes_supported, and the consent screen is all-or-nothing." Consent covers placing calls as the verified number and viewing call status, transcripts and recordings.
The docs state "DialMCP does not use OAuth scopes. The metadata has no scopes_supported, and the consent screen is all-or-nothing." Consent covers placing calls as the verified number and viewing call status, transcripts and recordings.
📄 Provider scope reference: https://dialmcp.com/docs/oauth
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.