generated: '2026-08-13' method: searched source: live /.well-known probes of Jasper hosts hosts: - host: https://api.jasper.ai documents: - path: /.well-known/openid-configuration status: 200 file: jasper-openid-configuration.json - path: /.well-known/oauth-authorization-server status: 200 file: jasper-oauth-authorization-server.json - path: /.well-known/security.txt 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 - host: https://mcp.jasper.ai documents: - path: /.well-known/oauth-authorization-server status: 200 file: jasper-mcp-oauth-authorization-server.json note: RFC 8414 authorization-server metadata for the hosted MCP server (issuer https://mcp.jasper.ai). - path: /.well-known/oauth-protected-resource status: 200 file: jasper-mcp-oauth-protected-resource.json note: >- RFC 9728 protected-resource metadata. resource https://mcp.jasper.ai, resource_name "Jasper MCP", scopes_supported [mcp], bearer_methods_supported [header]. - path: /.well-known/openid-configuration status: 200 file: jasper-mcp-openid-configuration.json - path: /.well-known/agent-card.json status: 404 - path: /.well-known/agent.json status: 404 - host: https://www.jasper.ai documents: - path: /.well-known/api-catalog status: 200 file: jasper-api-catalog.json - path: /.well-known/security.txt status: 404 - path: /.well-known/agent-card.json status: 404 - path: /.well-known/agent.json status: 404 - host: https://developers.jasper.ai documents: - path: /.well-known/security.txt status: 404 - path: /.well-known/openid-configuration status: 404 - path: /.well-known/agent-card.json status: 404 - path: /.well-known/agent.json status: 404 - host: https://app.jasper.ai documents: - path: /.well-known/agent-card.json status: 404 - path: /.well-known/agent.json status: 404 notes: >- Jasper publishes OIDC discovery and an RFC 8414 OAuth authorization-server document at api.jasper.ai (issuer https://api.jasper.ai, PKCE S256, Dynamic Client Registration at /oauth2/register), plus an RFC 9727 api-catalog linkset at www.jasper.ai pointing to the developer docs and API reference. This round added the MCP host: mcp.jasper.ai serves its own RFC 8414 authorization-server metadata AND an RFC 9728 oauth-protected-resource document (resource_name "Jasper MCP", scope `mcp`) — the discovery pair an MCP client uses to negotiate OAuth before calling tools/list. No security.txt was published on any probed host, and no A2A agent card was found at either the canonical or legacy well-known path on any of the five hosts.