Amphenol · OAuth Scopes

Amphenol OAuth Scopes

OAuth 2.0 probed

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

Electronic ConnectorsInterconnect SystemsFiber OpticsSensorsAerospaceAutomotiveDefenseManufacturingFortune 500
Scopes: 0 Flows: Method: probed

Scopes (0)

Amphenol 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:

Source

OAuth Scopes

amphenol-scopes.yml Raw ↑ 
generated: '2026-09-02'
method: probed
source: https://amphenol-automotive.com/.well-known/oauth-authorization-server
provider: Amphenol
providerId: amphenol
description: >-
  The only OAuth scope Amphenol publishes anywhere is the single scope "mcp", declared in the
  RFC 8414 authorization server metadata document served by Amphenol Automotive and repeated in
  its RFC 9728 protected resource metadata. There is no scope reference page, no permissions
  matrix, and no finer-grained scope: the whole Model Context Protocol resource sits behind one
  coarse grant.
authorization_server: https://amphenol-automotive.com
resource: https://amphenol-automotive.com/wp-json/mcp/mcp-oauth-server
scope_count: 1
scopes:
  - name: mcp
    description: >-
      Grants access to the Amphenol Automotive Model Context Protocol resource. The provider
      publishes no description of what the scope permits; the name is taken verbatim from the
      scopes_supported array in the metadata document. What it actually authorises could not be
      determined without an authenticated tools/list call.
    source: /.well-known/oauth-authorization-server
    granularity: coarse
docs: null
docs_note: No scopes or permissions reference page exists to enrich these definitions.
x-evidence:
  - url: https://amphenol-automotive.com/.well-known/oauth-authorization-server
    status: 200
  - url: https://amphenol-automotive.com/.well-known/oauth-protected-resource
    status: 200
checked: '2026-09-02'
maintainers:
  - FN: API Evangelist
    email: info@apievangelist.com

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