AllMCPs · OAuth Scopes
AllMCPs OAuth Scopes
OAuth 2.0
derived
AllMCPs publishes 2 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the AllMCPs API on a user’s behalf.
Tokens are issued from https://allmcps.com/api/v1/agent/register/confirm.
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.
DirectoryMCPAI AgentsDeveloper ToolsSearch & Data ExtractionFinance & FintechCommunicationsKnowledge & Memory
Scopes: 2
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://allmcps.com/api/v1/agent/register/confirm
https://allmcps.com/api/v1/agent/register/confirm
Flows
clientCredentials
clientCredentials
Scopes (2)
| Scope | Description | Flows |
|---|---|---|
| checkout:write | Create, update, complete and cancel Agentic Commerce Protocol checkout sessions to buy listing boosts. Payment still needs a Stripe shared payment token the buyer granted; this scope alone cannot spend money. Required by: ACP: /api/acp/checkout_sessions (all endpoints). | clientCredentials |
| listings:claim | Claim ownership of an existing MCP server listing via DNS TXT record, site verification badge, or GitHub README badge proof. Grants no other write access. Required by: POST /api/v1/agent/claim, MCP tool: verify_mcp_claim (with an agentToken). | clientCredentials |
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.