generated: '2026-09-02'
method: probed
source: >-
  live probes of Amphenol hosts; each entry's evidence names the exact URL and what it returned
provider: Amphenol
providerId: amphenol
description: >-
  Standards conformance asserted only where a live Amphenol surface demonstrated it. Amphenol
  publishes no compliance or standards page reachable to this run — the corporate host returns
  HTTP 403 at the CDN edge to non-browser clients — so nothing here rests on a marketing claim.
  Where a standard was not met, that is recorded as conforms: false rather than omitted.
conformance:
  - id: oauth2
    name: OAuth 2.0
    conforms: true
    evidence: >-
      amphenol-automotive.com serves a complete authorization-server metadata document with
      issuer, authorization_endpoint, token_endpoint and revocation_endpoint, and its protected
      resource returns HTTP 401 with a WWW-Authenticate-style JSON challenge.
    source: https://amphenol-automotive.com/.well-known/oauth-authorization-server
    status: 200
  - id: rfc8414
    name: 'RFC 8414 — OAuth 2.0 Authorization Server Metadata'
    conforms: true
    evidence: >-
      /.well-known/oauth-authorization-server returns HTTP 200 application/json carrying issuer,
      authorization_endpoint, token_endpoint, response_types_supported, grant_types_supported,
      code_challenge_methods_supported, scopes_supported and
      token_endpoint_auth_methods_supported.
    source: https://amphenol-automotive.com/.well-known/oauth-authorization-server
    status: 200
  - id: rfc9728
    name: 'RFC 9728 — OAuth 2.0 Protected Resource Metadata'
    conforms: true
    evidence: >-
      /.well-known/oauth-protected-resource returns HTTP 200 naming resource,
      authorization_servers, bearer_methods_supported and scopes_supported. This is the
      discovery document an MCP client needs to find the authorization server from the resource.
    source: https://amphenol-automotive.com/.well-known/oauth-protected-resource
    status: 200
  - id: rfc7636
    name: 'RFC 7636 — PKCE'
    conforms: true
    evidence: code_challenge_methods_supported is ["S256"]; plain is not offered.
    source: https://amphenol-automotive.com/.well-known/oauth-authorization-server
    status: 200
  - id: mcp
    name: Model Context Protocol
    conforms: partial
    evidence: >-
      A live MCP resource is registered and advertised, and it rejects unauthenticated JSON-RPC
      with a protocol-shaped 401. Full conformance could not be established because tools/list
      is auth-gated, so the initialize handshake, protocolVersion and tool schemas were never
      seen.
    source: https://amphenol-automotive.com/wp-json/mcp/mcp-oauth-server
    status: 401
  - id: rfc9457
    name: 'RFC 9457 — Problem Details for HTTP APIs'
    conforms: false
    evidence: >-
      No endpoint returns application/problem+json. Two ad-hoc JSON error envelopes are in use
      across the company's hosts. See errors/amphenol-problem-types.yml.
    source: https://amphenol-industrial.com/wp-json/parts-direct-search/v1/search
    status: 400
  - id: rfc9116
    name: 'RFC 9116 — security.txt'
    conforms: false
    evidence: >-
      404 on amphenol-automotive.com and amphenolsensors.com; amphenol-industrial.com answers
      200 with its HTML homepage, a soft-404, not an RFC 9116 document; 403 at the edge on the
      corporate hosts.
    source: https://amphenol-industrial.com/.well-known/security.txt
    status: 200
  - id: pagination
    name: Collection pagination
    conforms: false
    evidence: The search endpoint accepts no page, per_page, limit, offset or cursor parameter.
    source: https://amphenol-industrial.com/wp-json/parts-direct-search/v1/search
    status: 200
  - id: idempotency
    name: Idempotency keys
    conforms: na
    evidence: 'No write surface is reachable; the search endpoint advertises Allow: GET.'
  - id: openapi
    name: OpenAPI
    conforms: false
    evidence: >-
      No OpenAPI or Swagger document was served at /openapi.json, /openapi.yaml, /swagger.json,
      /api-docs or /docs on any reachable Amphenol host. The only machine-readable route
      description that exists is the WordPress REST index at /wp-json/, which is a route
      descriptor, not an API contract.
    source: https://amphenol-industrial.com/openapi.json
    status: 404
  - id: llmstxt
    name: llms.txt
    conforms: true
    evidence: >-
      Three Amphenol division hosts serve a real llms.txt: amphenolsensors.com (hand-authored,
      1,572 bytes), amphenol-industrial.com (generated by Rank Math SEO, 6,255 bytes) and
      amphenol-automotive.com (hand-authored "GEO optimized" content map, 3,734 bytes).
    source: https://amphenolsensors.com/llms.txt
    status: 200
domain_standards:
  probed: true
  found: false
  note: >-
    Amphenol's market is electronic interconnect manufacturing, whose interchange standards are
    supply-chain formats rather than web-API standards. No SCIM URN, OData $metadata, OpenRTB,
    Sparkplug topic namespace, ActivityPub actor, OAI-PMH verb, LTI/OneRoster shape, HL7v2, X12,
    EDIFACT or ISO 20022 message type appears in any surface probed. Amphenol's own plans
    artifact records that distributor exchange is bilateral EDI, which would be the place an X12
    or EDIFACT signature could live, but no such contract is published: the exchange is
    partner-private. This is REWARD-ONLY — no domain standard is invented to fill the slot.
  candidates_checked:
    - scim
    - odata
    - x12
    - edifact
    - iso20022
    - sparkplug
certifications:
  found: false
  note: >-
    No trust centre, no SOC 2 / ISO 27001 / PCI / HIPAA / FedRAMP attestation page was reachable.
    probe-security-programs.py returned vdp=none trust=none. No Compliance pointer is emitted,
    because emitting one would assert a published compliance programme that this run could not
    find.
checked: '2026-09-02'
maintainers:
  - FN: API Evangelist
    email: info@apievangelist.com