Mireye · OAuth Scopes

Mireye OAuth Scopes

OAuth 2.0 searched

Mireye publishes 1 OAuth 2.0 scope via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Mireye API on a user’s behalf.

Tokens are issued from https://api.mireye.com/token.

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.

CompanyGeospatialGeographic Information SystemLocationAI AgentsModel Context ProtocolGovernment DataRiskInsuranceData

Scopes: 1 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://api.mireye.com/authorize

Token URL
https://api.mireye.com/token

Flows
authorizationCode

Scopes (1)

Scope	Description	Flows
mcp:tools	Authorizes calls to Mireye's MCP tools (mireye_ask, mireye_fetch) via the hosted /mcp endpoint. Not valid for direct /v1/* HTTP API calls.	authorizationCode

📄 Provider scope reference: https://docs.mireye.ai/authentication

Source

OAuth Scopes

generated: '2026-07-20'
method: searched
source: https://api.mireye.com/.well-known/oauth-authorization-server
docs: https://docs.mireye.ai/authentication
note: >-
  Scopes captured from the RFC 8414 authorization-server metadata and the auth docs; the
  OpenAPI declares no oauth2 securitySchemes so nothing was derivable from the spec.
schemes:
- name: mcpOAuth
  source: https://api.mireye.com/.well-known/oauth-authorization-server
  flows:
  - flow: authorizationCode
    authorizationUrl: https://api.mireye.com/authorize
    tokenUrl: https://api.mireye.com/token
    code_challenge_methods: [S256]
scopes:
- scope: mcp:tools
  description: Authorizes calls to Mireye's MCP tools (mireye_ask, mireye_fetch) via the hosted /mcp endpoint. Not valid for direct /v1/* HTTP API calls.
  flows: [authorizationCode]
  sources: ['https://api.mireye.com/.well-known/oauth-authorization-server']