Clarifeye · OAuth Scopes

Clarifeye OAuth Scopes

OAuth 2.0 searched

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

Tokens are issued from https://eu.app.clarifeye.ai/o/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.

CompanyArtificial IntelligenceKnowledge-ManagementMCPDocument IntelligenceAgentsEnterprise AIRetrieval

Scopes: 3 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://eu.app.clarifeye.ai/o/authorize/

Token URL
https://eu.app.clarifeye.ai/o/token/

Flows
authorizationCode

Scopes (3)

Scope	Description	Flows
claudeai	MCP access scope for Claude / AI-client connectors to the Clarifeye knowledge stores.	authorizationCode
openid	OpenID Connect scope; identifies the authenticated user (whoami).	authorizationCode
offline_access	Requests a refresh token so the client can maintain access without re-consent.	authorizationCode

📄 Provider scope reference: https://docs.clarifeye.ai/guides/mcp-authentication

Source

OAuth Scopes

generated: '2026-07-18'
method: searched
source: https://eu.app.clarifeye.ai/.well-known/oauth-authorization-server
docs: https://docs.clarifeye.ai/guides/mcp-authentication
note: >
  Clarifeye's OAuth surface backs the hosted MCP server, not the REST API
  (the REST OpenAPI declares only Bearer token / Token apiKey auth). Scopes
  are enumerated by the OAuth authorization-server discovery document and by
  the MCP authentication guide. Dynamic Client Registration (RFC 7591) is
  supported at /o/register/; PKCE S256 required.
schemes:
- name: OAuth2
  source: https://eu.app.clarifeye.ai/.well-known/oauth-authorization-server
  flows:
  - flow: authorizationCode
    authorizationUrl: https://eu.app.clarifeye.ai/o/authorize/
    tokenUrl: https://eu.app.clarifeye.ai/o/token/
    refreshUrl: https://eu.app.clarifeye.ai/o/token/
    registrationUrl: https://eu.app.clarifeye.ai/o/register/
    revocationUrl: https://eu.app.clarifeye.ai/o/revoke/
scopes:
- scope: claudeai
  description: MCP access scope for Claude / AI-client connectors to the Clarifeye knowledge stores.
  flows: [authorizationCode]
  sources: [https://eu.app.clarifeye.ai/.well-known/oauth-authorization-server]
- scope: openid
  description: OpenID Connect scope; identifies the authenticated user (whoami).
  flows: [authorizationCode]
  sources: [https://eu.app.clarifeye.ai/.well-known/oauth-authorization-server]
- scope: offline_access
  description: Requests a refresh token so the client can maintain access without re-consent.
  flows: [authorizationCode]
  sources: [https://eu.app.clarifeye.ai/.well-known/oauth-authorization-server]

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