StayingAPI · OAuth Scopes

StayingAPI OAuth Scopes

OAuth 2.0 searched

StayingAPI 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 StayingAPI API on a user’s behalf.

Tokens are issued from https://mcp.stayingapi.com/mcp/oauth/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.

travelhospitalityaccommodation-datahotel-apivacation-rentalshort-term-rentalairbnbbooking.comvrbogoogle-hotelscross-ota-price-comparisonavailabilityreviewsrestmcpagent-nativeopenapi

Scopes: 1 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://mcp.stayingapi.com/mcp/oauth/authorize

Token URL
https://mcp.stayingapi.com/mcp/oauth/token

Flows
authorizationCode

Scopes (1)

Scope	Description	Flows
stays.read	Read-only access to StayingAPI accommodation data through the MCP server — search, availability, listing detail, price, cross-OTA price comparison, reviews and job polling. No write scope is published; every MCP tool is read-only.	authorizationCode

📄 Provider scope reference: https://stayingapi.com/docs/mcp

Source

OAuth Scopes

generated: '2026-08-09'
method: searched
source: https://mcp.stayingapi.com/.well-known/oauth-authorization-server
docs: https://stayingapi.com/docs/mcp
description: >-
  StayingAPI's OAuth surface belongs to the hosted MCP server, not the REST API (REST uses a
  Bearer API key with no scopes). A single read scope is advertised by both the RFC 8414
  authorization-server metadata and the RFC 9728 protected-resource metadata, which matches
  the server's posture of seven read-only tools.
schemes:
  - name: mcpOAuth
    source: well-known/stayingapi-oauth-authorization-server.json
    resource: https://mcp.stayingapi.com/mcp
    authorization_servers:
      - https://mcp.stayingapi.com/mcp/oauth
    flows:
      - flow: authorizationCode
        authorizationUrl: https://mcp.stayingapi.com/mcp/oauth/authorize
        tokenUrl: https://mcp.stayingapi.com/mcp/oauth/token
        registrationUrl: https://mcp.stayingapi.com/mcp/oauth/register
        code_challenge_methods:
          - S256
scopes:
  - scope: stays.read
    description: >-
      Read-only access to StayingAPI accommodation data through the MCP server — search,
      availability, listing detail, price, cross-OTA price comparison, reviews and job
      polling. No write scope is published; every MCP tool is read-only.
    flows:
      - authorizationCode
    sources:
      - well-known/stayingapi-oauth-authorization-server.json
      - well-known/stayingapi-oauth-protected-resource.json
notes:
  - The REST OpenAPI declares only http/bearer; it has no oauth2 securityScheme and therefore
    no spec-derived scopes.
  - >-
    An insufficient-scope condition is present in the REST error catalog as sub-code
    scope_insufficient (403 permission_denied).
x-evidence:
  - url: https://mcp.stayingapi.com/.well-known/oauth-authorization-server
    http_status: 200
  - url: https://mcp.stayingapi.com/.well-known/oauth-protected-resource
    http_status: 200