Micro Connect · OAuth Scopes

Micro Connect OAuth Scopes

OAuth 2.0 probed

Micro Connect 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.

CompanyFinancial-ServicesCapital MarketsExchangesRevenue-Based FinancingFintechInvestingSmall BusinessHong KongMacaoChina

Scopes: 0 Flows: Method: probed

Scopes (0)

Micro Connect 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.

These are the OpenID Connect / Keycloak built-in client scopes the numa-realm authorisation server advertises anonymously. Micro Connect publishes NO business-domain scope reference — there is no documented scope for revenue reporting, order-detail submission, settlement export or any other Open Platform capability. Authorisation for those capabilities is carried in Keycloak realm/client ROLES inside the access token (the Open Platform bundle reads resource_access[clientId].roles), and that role catalogue is not published. Do not read this list as an API permission model; it is the identity layer only.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-25'
method: probed
source: >-
  scopes_supported read verbatim from
  https://kc.mcisaas.com/auth/realms/numa-realm/.well-known/openid-configuration (HTTP 200),
  saved in well-known/micro-connect-kc-numa-realm-openid-configuration.json
docs: null
note: >-
  These are the OpenID Connect / Keycloak built-in client scopes the numa-realm authorisation
  server advertises anonymously. Micro Connect publishes NO business-domain scope reference —
  there is no documented scope for revenue reporting, order-detail submission, settlement
  export or any other Open Platform capability. Authorisation for those capabilities is
  carried in Keycloak realm/client ROLES inside the access token (the Open Platform bundle
  reads resource_access[clientId].roles), and that role catalogue is not published. Do not
  read this list as an API permission model; it is the identity layer only.
authorization_server: https://kc.mcisaas.com/auth/realms/numa-realm
scope_count: 10
scopes:
- name: openid
  description: Required OpenID Connect scope; requests an ID token.
  standard: true
- name: profile
  description: Standard OIDC profile claims (name, given_name, family_name, preferred_username).
  standard: true
- name: email
  description: Standard OIDC email claim.
  standard: true
- name: phone
  description: Standard OIDC phone_number claims.
  standard: true
- name: address
  description: Standard OIDC address claim.
  standard: true
- name: roles
  description: Keycloak built-in scope; adds realm and client role mappings to the token.
  standard: false
- name: web-origins
  description: Keycloak built-in scope; adds allowed CORS origins to the token.
  standard: false
- name: offline_access
  description: Requests an offline refresh token.
  standard: true
- name: microprofile-jwt
  description: Keycloak built-in scope; adds MicroProfile JWT claims (upn, groups).
  standard: false
- name: acr
  description: Authentication Context Class Reference; realm advertises acr_values 0 and 1.
  standard: true

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/micro-connect-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 email required.

GitHub Google LinkedIn

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