Luminary Lane · OAuth Scopes

Luminary Lane OAuth Scopes

OAuth 2.0 probed

Luminary Lane 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.

CompanyMarketingMarketing AutomationAI AgentsAgent-NativeMCPA2ABrand ManagementContent GenerationCampaign ManagementSocial MediaSoftware-as-a-Service
Scopes: 0 Flows: Method: probed

Scopes (0)

Luminary Lane 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.

Source

OAuth Scopes

luminarylane-app-scopes.yml Raw ↑
generated: '2026-09-19'
method: probed
source: https://mcp.luminarylane.app/.well-known/oauth-authorization-server
docs: https://github.com/luminarylane/lane-plugin
corroborating_source: https://mcp.luminarylane.app/.well-known/oauth-protected-resource/mcp
scope_count: 0
summary: >-
  Luminary Lane publishes no OpenAPI (derive-oauth-scopes.py reports 0 oauth2 providers for this repo),
  so this file records what the live RFC 8414 / RFC 9728 discovery documents on the MCP host declare.
  Neither document carries scopes_supported, the provider documents no scope or permission vocabulary
  anywhere public, and the alternative X-API-Key credential is a per-user key with no scoping surface.
  An OAuth client therefore requests a token with no scope parameter and receives whatever the signed-in
  user's workspace access allows. The absence is the measurement; no scope names were invented.
model: >-
  Unscoped OAuth 2.1 authorization-code + PKCE against a first-party authorization server co-hosted with
  the MCP resource. Authorization is workspace/brand-membership based, not scope based.
authorization_server:
  issuer: https://mcp.luminarylane.app/
  vendor: first-party (Express)
  metadata_url: https://mcp.luminarylane.app/.well-known/oauth-authorization-server
  http_status: 200
  authorization_endpoint: https://mcp.luminarylane.app/authorize
  token_endpoint: https://mcp.luminarylane.app/token
  revocation_endpoint: https://mcp.luminarylane.app/revoke
  registration_endpoint: https://mcp.luminarylane.app/register
  grant_types_supported:
    - authorization_code
    - refresh_token
  response_types_supported:
    - code
  code_challenge_methods_supported:
    - S256
  token_endpoint_auth_methods_supported:
    - client_secret_post
    - none
  revocation_endpoint_auth_methods_supported:
    - client_secret_post
  scopes_supported: null
  jwks_uri: null
protected_resource:
  metadata_url: https://mcp.luminarylane.app/.well-known/oauth-protected-resource/mcp
  http_status: 200
  resource: https://mcp.luminarylane.app/mcp
  resource_name: Luminary Lane MCP Server
  authorization_servers:
    - https://mcp.luminarylane.app/
  scopes_supported: null
  bearer_methods_supported: null
scopes: []

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This scope set
curl "https://apis.io/api/v1/scopes/luminarylane-app-scopes"
All oauth scopes
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.