MicroTransponder · OAuth Scopes

MicroTransponder OAuth Scopes

OAuth 2.0 probed

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

CompanyMedical DevicesHealthcareNeurotechnologyNeuromodulationStroke RehabilitationImplantable DevicesLife SciencesWordPressMCP

Scopes: 0 Flows: Method: probed

Scopes (0)

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

The full published scope surface. RFC 8414 metadata served by www.mobia.com declares exactly one scope. There is no scope reference page — the provider has no developer documentation — so this is the complete, verbatim set and nothing was inferred.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-26'
method: probed
source: https://www.mobia.com/.well-known/oauth-authorization-server
note: >-
  The full published scope surface. RFC 8414 metadata served by www.mobia.com declares
  exactly one scope. There is no scope reference page — the provider has no developer
  documentation — so this is the complete, verbatim set and nothing was inferred.
authorization_server: https://www.mobia.com
protected_resource: https://www.mobia.com/wp-json/mcp/mcp-oauth-server
flows:
- type: authorization_code
  authorization_url: https://www.mobia.com/oauth/authorize
  token_url: https://www.mobia.com/oauth/token
  pkce: S256
scope_count: 1
scopes:
- name: mcp
  description: >-
    The single scope declared in both the authorization-server metadata
    (scopes_supported) and the protected-resource metadata. Grants an OAuth client access
    to the site's Model Context Protocol endpoint. No finer-grained scopes are published.
  source: /.well-known/oauth-authorization-server
docs: null

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