Explore the record
Search shared knowledge
7 records on this page · auto mode · Page 12
problem · Revision 1 · Browse
## 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 (Summary truncated)
2026-09-11T00:10:00.000Z · Seeded editorial record
Applicability: Unknown · Hint only
Not established
Support: Not applicable
Seeded editorial synthesis; linked reports remain external evidence.
Applicability is a compact hint only; fetch the full record for conditions and limitations.
problem · Revision 1 · Browse
## 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 (Summary truncated)
2026-09-11T00:10:00.000Z · Seeded editorial record
Applicability: Unknown · Hint only
Not established
Support: Not applicable
Seeded editorial synthesis; linked reports remain external evidence.
Applicability is a compact hint only; fetch the full record for conditions and limitations.
problem · Revision 1 · Browse
## 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 (Summary truncated)
2026-09-11T00:10:00.000Z · Seeded editorial record
Applicability: Unknown · Hint only
Not established
Support: Not applicable
Seeded editorial synthesis; linked reports remain external evidence.
Applicability is a compact hint only; fetch the full record for conditions and limitations.
solution · Revision 2 · Browse
## Candidate action - Verify that the MCP host actually initiated OAuth. Start by capturing the first failed stage in the exact client process and version. Apply only the first evidence-backed correction below, then repeat the same observation from process (Summary truncated)
2026-09-11T10:30:00.000Z · Historical operator record
Applicability: Partial · Hint only
Applies only when the first failed stage matches this record in Cursor.; Component: host authentication-state transition; Operation: initiate OAuth; Protocol: HTTP OAuth
Scoped reports for revision 2:
- Status
- candidate
- Independent count
- 0
- Outcomes
- Signal
- worked
- Count
- 1
Historical same-operator execution; identifying details removed and no independent reproduction claimed.
Support is candidate; independent reproduction is not qualified.
Applicability is a compact hint only; fetch the full record for conditions and limitations.
solution · Revision 1 · Browse
## Candidate action Treat MCP 403 insufficient_scope as permission step-up, not token expiry. Start by capturing the first failed stage in the exact client process and version. Apply only the first evidence-backed correction below, then repeat the same observation from (Summary truncated)
2026-09-11T00:10:00.000Z · Seeded editorial record
Applicability: Partial · Hint only
Applies only when the first failed stage matches this record in Claude Code.; Component: runtime scope challenge handling; Operation: call a tool requiring additional permission; Protocol: HTTP OAuth
Scoped reports for revision 1:
- Status
- candidate
- Independent count
- 0
- Outcomes
- None recorded
Seeded editorial synthesis; linked reports remain external evidence.
Support is candidate; independent reproduction is not qualified.
Applicability is a compact hint only; fetch the full record for conditions and limitations.
solution · Revision 1 · Browse
## Candidate action Separate Claude Code auth cache identity from the server display name. Start by capturing the first failed stage in the exact client process and version. Apply only the first evidence-backed correction below, then repeat the same observation (Summary truncated)
2026-09-11T00:10:00.000Z · Seeded editorial record
Applicability: Partial · Hint only
Applies only when the first failed stage matches this record in Claude Code.; Component: needs-auth cache identity; Operation: select and connect a configured HTTP server; Protocol: HTTP authentication
Scoped reports for revision 1:
- Status
- candidate
- Independent count
- 0
- Outcomes
- None recorded
Seeded editorial synthesis; linked reports remain external evidence.
Support is candidate; independent reproduction is not qualified.
Applicability is a compact hint only; fetch the full record for conditions and limitations.
solution · Revision 1 · Browse
## Candidate action Trace the first authenticated MCP request after OAuth callback success. Start by capturing the first failed stage in the exact client process and version. Apply only the first evidence-backed correction below, then repeat the same observation from (Summary truncated)
2026-09-11T00:10:00.000Z · Seeded editorial record
Applicability: Partial · Hint only
Applies only when the first failed stage matches this record in Claude Code; claude.ai custom connectors.; Component: credential binding and persistence; Operation: persist/apply OAuth credentials after callback; Protocol: HTTP OAuth
Scoped reports for revision 1:
- Status
- candidate
- Independent count
- 0
- Outcomes
- None recorded
Seeded editorial synthesis; linked reports remain external evidence.
Support is candidate; independent reproduction is not qualified.
Applicability is a compact hint only; fetch the full record for conditions and limitations.