CI HUB · OAuth Scopes

CI HUB OAuth Scopes

OAuth 2.0 probed

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

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.

CompanyDigital Asset ManagementContent ManagementProduct Information ManagementIntegrationConnectorsCreative ToolsMarketingBrand ManagementMCPCloud StorageGermany

Scopes: 1 Flows: Method: probed

Scopes (1)

Scope	Description	Flows
cihub	The single scope advertised by the CI HUB MCP authorization server. It is coarse: it does not subdivide by asset operation, by DAM provider, or by read versus write. Effective authority is not decided by this scope but downstream — each end user separately authenticates the DAM accounts they want reachable, and CI HUB maps that user's existing DAM permissions onto every tool call. A consumer cannot narrow an MCP client's authority through the OAuth grant; the narrowing happens in the DAM.

📄 Provider scope reference: https://ci-hub.com/ai/mcp-server

Source

OAuth Scopes

generated: '2026-08-12'
method: probed
source: https://mcp-auth.ci-hub.com/.well-known/oauth-authorization-server
docs: https://ci-hub.com/ai/mcp-server
note: >-
  The Access SDK HTTP API has no OAuth scope surface — it authenticates by partner-JWT token
  exchange plus a per-DAM connection token, so derive-oauth-scopes.py correctly found nothing
  there. The scope surface belongs to the MCP server: mcp.ci-hub.com is an OAuth 2.1 protected
  resource whose authorization server publishes RFC 8414 metadata anonymously. That metadata
  declares exactly one scope. Values below are read verbatim from the live document; nothing is
  inferred.
applies_to: ci-hub:mcp
authorization_server: https://mcp-auth.ci-hub.com
endpoints:
  authorization: https://mcp-auth.ci-hub.com/authorize
  token: https://mcp-auth.ci-hub.com/token
  userinfo: https://mcp-auth.ci-hub.com/userinfo
  jwks: https://mcp-auth.ci-hub.com/jwks.json
  registration: https://mcp-auth.ci-hub.com/register
flows:
  grant_types:
  - authorization_code
  - refresh_token
  response_types:
  - code
  response_modes:
  - query
  code_challenge_methods:
  - S256
  token_endpoint_auth_methods:
  - client_secret_basic
  - client_secret_post
  - none
  dynamic_client_registration: true
  subject_types:
  - public
  id_token_signing_alg:
  - RS256
scopes:
- name: cihub
  description: >-
    The single scope advertised by the CI HUB MCP authorization server. It is coarse: it does not
    subdivide by asset operation, by DAM provider, or by read versus write. Effective authority
    is not decided by this scope but downstream — each end user separately authenticates the DAM
    accounts they want reachable, and CI HUB maps that user's existing DAM permissions onto every
    tool call. A consumer cannot narrow an MCP client's authority through the OAuth grant; the
    narrowing happens in the DAM.
  source: authorization-server-metadata
claims_supported:
- sub
- iss
- aud
- exp
- iat
- scope
summary:
  scope_count: 1
  granularity: coarse
  read_write_split: false
  per_provider_scopes: false
x-evidence:
  fetched: '2026-08-12'
  checks:
  - url: https://mcp-auth.ci-hub.com/.well-known/oauth-authorization-server
    http_status: 200
  - url: https://mcp-auth.ci-hub.com/.well-known/openid-configuration
    http_status: 200
  - url: https://mcp.ci-hub.com/.well-known/oauth-protected-resource
    http_status: 200

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/ci-hub-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.