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