generated: '2026-09-19'
method: probed
source: https://fusewp.com/.well-known/
note: 'Two real documents were served. fusewp.com publishes RFC 8414 OAuth Authorization Server Metadata
  and RFC 9728 OAuth Protected Resource Metadata, both of which resolve (via a 301 to the trailing-slash
  form) to genuine JSON and both of which advertise the `mcp` scope and the MCP endpoint at https://fusewp.com/wp-json/mcp/mcp-oauth-server.
  These are emitted by the WordPress MCP Adapter running on FuseWP''s own WordPress site, not by a purpose-built
  FuseWP identity service — but the provider does serve them from its own host, which is what the pointer
  asserts. No security.txt, no openid-configuration, no api-catalog, no ai-plugin.json and no agent card
  on either host. The OAuth broker host auth.fusewp.com serves no /.well-known/ surface at all.


  MCP-host OAuth discovery added 2026-09-19 (roadmap#321/#337): the harvest visits a provider''s primary
  hosts, and RFC 9728 protected-resource metadata lives on the MCP host, so these documents existed and
  were invisible to the scorer. Fetched live and validated on `resource`/`issuer`; one negative control
  per host.'
hosts:
- host: https://fusewp.com
  documents:
  - path: /.well-known/oauth-authorization-server
    status: 301
    redirects_to: /.well-known/oauth-authorization-server/
    final_status: 200
    content_type: application/json
    file: fusewp-oauth-authorization-server.json
    spec: RFC 8414
  - path: /.well-known/oauth-protected-resource
    status: 301
    redirects_to: /.well-known/oauth-protected-resource/
    final_status: 200
    content_type: application/json
    file: fusewp-oauth-protected-resource.json
    spec: RFC 9728
  - path: /.well-known/security.txt
    status: 404
  - path: /.well-known/openid-configuration
    status: 404
  - path: /.well-known/api-catalog
    status: 404
  - path: /.well-known/ai-plugin.json
    status: 404
  - path: /.well-known/agent-card.json
    status: 404
  - path: /.well-known/agent.json
    status: 404
  - path: /.well-known/mcp.json
    status: 404
  - path: /.well-known/oauth-protected-resource
    status: 200
    file: fusewp-fusewp-oauth-protected-resource.json
    bytes: 181
  - path: /.well-known/oauth-authorization-server
    status: 200
    file: fusewp-fusewp-oauth-authorization-server.json
    bytes: 531
  path_echo_control: passed
- host: https://auth.fusewp.com
  documents:
  - path: /.well-known/security.txt
    status: 404
  - path: /.well-known/openid-configuration
    status: 404
  - path: /.well-known/oauth-authorization-server
    status: 404
  - path: /.well-known/oauth-protected-resource
    status: 404
  - path: /.well-known/api-catalog
    status: 404
  - path: /.well-known/ai-plugin.json
    status: 404
  - path: /.well-known/agent-card.json
    status: 404
  - path: /.well-known/agent.json
    status: 404
  - path: /.well-known/mcp.json
    status: 404
x-evidence:
  fetched: '2026-08-12'
  hosts_probed: 2
  paths_probed: 18
  documents_returned: 2
x-mcp-probe:
  probed: '2026-09-19'
  issue: roadmap#321, roadmap#337
  documents:
  - host: https://fusewp.com
    path: /.well-known/oauth-protected-resource
    file: fusewp-fusewp-oauth-protected-resource.json
  - host: https://fusewp.com
    path: /.well-known/oauth-authorization-server
    file: fusewp-fusewp-oauth-authorization-server.json
  validated_on: resource (RFC 9728) / issuer (RFC 8414, OIDC)
  negative_control: one per host; a 2xx JSON object at an impossible path discards the host