problem · Revision 1
## Problem - MCP protected-resource metadata is published at the wrong path ## Observed symptom - OAuth discovery probes the RFC 9728 protected-resource metadata URL and receives 404 or non-metadata content. - Observed in 1 reviewed public artifact; this is
problem · Revision 1
## Problem - MCP OAuth metadata advertises an internal origin behind a reverse proxy ## Observed symptom - The MCP 401 challenge points clients to an internal host or omits the public ingress base path. - Observed in 1 reviewed
problem · Revision 1
## Problem - MCP TypeScript OAuth token exchange targets the resource server instead of a separate authorization server ## Observed symptom - Initial OAuth opens, but finishAuth posts to the MCP resource host and returns an invalid API path or
problem · Revision 1
## Problem - MCP OAuth discovery drops a sub-path before well-known lookup ## Observed symptom - A path-mounted MCP resource fails metadata discovery because the client probes only domain-root well-known endpoints. - Observed in 2 reviewed public artifacts; this is
problem · Revision 1
## Problem - OAuth metadata discovery is attempted for an API-key-only MCP server ## Observed symptom - Inspector reports Failed to discover OAuth metadata when OAuth is selected for a server that expects an API key/header instead. - Observed in
problem · Revision 1
## Problem - Claude Code connects with hasTools true but does not expose the tool to the model ## Observed symptom - Connection diagnostics indicate tools exist, yet the requested mcp__ tool is absent from the model session. - Observed
problem · Revision 1
## Problem - Cursor extension-registered MCP server stays at 0 tools enabled ## Observed symptom - A server registered through Cursor's extension API remains enabled but exposes zero tools until host state changes. - Observed in 1 reviewed public artifact;
problem · Revision 1
## Problem - Cursor shows 0 tools even though the MCP command starts outside Cursor ## Observed symptom - Cursor lists the server enabled with 0 tools, while running the command directly does not expose an obvious startup failure. -
problem · Revision 1
## Problem - MCP tools are discovered but disabled or hidden by host controls ## Observed symptom - A server is configured or connected, but its tools are unavailable to the current agent/profile because trust, enablement, or policy excludes them.
problem · Revision 1
## Problem - MCP tool is omitted because its input schema is invalid for the host ## Observed symptom - The server connects, but one or more tools are absent or the host reports an invalid tool input schema. -
problem · Revision 1
## Problem - No server info found after the MCP process failed to start ## Observed symptom - The host shows No server info found or no tools after an earlier subprocess launch error. - Observed in 2 reviewed public
problem · Revision 1
## Problem - MCP Streamable HTTP returns unexpected text/html content type ## Observed symptom - The client expects an MCP JSON or request-scoped SSE response but receives text/html. - Observed in 1 reviewed public artifact; this is not a claim
problem · Revision 1
## Problem - MCP client and endpoint disagree between legacy SSE and Streamable HTTP ## Observed symptom - A configured SSE endpoint works in direct tests, but the host reports a Streamable HTTP content-type/connection error or probes it with the
problem · Revision 1
## Problem - MCP server connection closes during initialize because logs are written to stdout ## Observed symptom - A stdio client reports connection closed: initialize response and logs show non-JSON-RPC lines arriving before the response. - Observed in 1