Cledara · OAuth Scopes

Cledara OAuth Scopes

OAuth 2.0 probed

Cledara 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.

FinanceSaaS ManagementSoftware SpendingSpend ManagementSubscription ManagementVirtual CardsExpense ManagementFinOpsMCPMarket Data
Scopes: 0 Flows: Method: probed

Scopes (0)

Cledara 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.

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-09-05'
method: probed
source: https://data.cledara.com/.well-known/oauth-authorization-server
provider: Cledara
providerId: cledara
description: >-
  OAuth scopes Cledara publishes. Exactly one, and it belongs to the market-data MCP
  endpoint, not to the workspace REST API — that surface authenticates with an unscoped
  Bearer API key that inherits the creating user's full permissions and therefore has no
  scope vocabulary at all.
api: Cledara SaaS Market Data Hub MCP Server
authorization_server: https://data.cledara.com
flows:
  - type: authorization_code
    authorizationUrl: https://data.cledara.com/authorize
    tokenUrl: https://data.cledara.com/oauth/token
    pkce: S256
  - type: client_credentials
    tokenUrl: https://data.cledara.com/oauth/token
scopes:
  - name: 'mcp:read'
    description: >-
      Read access to the Cledara SaaS Market Data Hub through the MCP endpoint at
      https://data.cledara.com/mcp. Declared in scopes_supported of the RFC 8414
      authorization-server metadata; Cledara publishes no prose scope reference, so the
      description here is derived from the scope name plus the endpoint it guards.
    grants: read
    surface: https://data.cledara.com/mcp
scope_count: 1
docs: null
notes:
  - No write scope is published, which is consistent with a read-only public dataset.
  - No scope reference page exists on the provider's site; the authorization-server
    metadata document is the only published source.
  - The REST API at api.cledara.com declares only an http/bearer securityScheme and
    therefore contributes no scopes.
maintainers:
  - FN: Kin Lane
    email: kinlane@gmail.com

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/cledara-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.

GitHub Google LinkedIn

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