TranscriptFetch · OAuth Scopes

TranscriptFetch OAuth Scopes

OAuth 2.0 probed

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

TranscriptsSpeech-to-TextCaptionsYouTubeTikTokInstagramPodcastsMCPllms-txtOpenAPITranscriptionVideoAI/LLMRAGAgentsDeveloper ToolsMediaContentSpotifyApple Podcasts
Scopes: 0 Flows: Method: probed

Scopes (0)

TranscriptFetch 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: https://transcriptfetch.com/docs/mcp

Source

OAuth Scopes

Raw ↑ 
generated: '2026-09-09'
method: probed
source: >-
  https://transcriptfetch.com/.well-known/oauth-protected-resource and
  https://clerk.transcriptfetch.com/.well-known/oauth-authorization-server (both HTTP
  200, fetched 2026-09-09). The REST OpenAPI declares only bearerAuth (API key), so
  derive-oauth-scopes.py found no oauth2 scheme; these scopes come from the served
  OAuth metadata, which governs the MCP surface.
docs: https://transcriptfetch.com/docs/mcp
surface: MCP server (https://transcriptfetch.com/mcp) via Clerk-run OAuth; REST API uses bearer API keys without scopes.
scopes:
- name: openid
  description: OpenID Connect authentication (standard OIDC scope).
- name: profile
  description: Access to basic profile claims (name, picture, preferred_username).
- name: email
  description: Access to the account email address and verification status.
- name: offline_access
  description: Refresh-token issuance for long-lived MCP client connections.
- name: public_metadata
  description: Clerk user public metadata (authorization-server metadata; not documented per-endpoint by TranscriptFetch).
- name: private_metadata
  description: Clerk user private metadata (authorization-server metadata; not documented per-endpoint by TranscriptFetch).
notes:
- The protected-resource document scopes_supported lists openid, profile, email, offline_access for the MCP resource.
- Identity scopes only — API authorization is account/credit-based, not scope-partitioned; there are no per-tool or per-endpoint scopes.

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