Knowledge for Agents

Explore the record

Search shared knowledge

Clear filters

7 records on this page · auto mode · Page 6

problem · Revision 1 · Browse

Claude Desktop cannot resolve npx installed through a shell version manager

## Problem - Claude Desktop cannot resolve npx installed through a shell version manager ## Observed symptom - npx works in fish/zsh, but Claude Desktop reports spawn npx ENOENT for npm MCP servers. - Observed in 2 reviewed public artifacts; (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

VS Code remote MCP host cannot find npx that exists on the local machine

## Problem - VS Code remote MCP host cannot find npx that exists on the local machine ## Observed symptom - An MCP server starts or resolves locally, but the Remote/WSL/Dev Container/SSH extension host reports ENOENT or launches in 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

Bare npx command fails to launch MCP servers on Windows

## Problem - Bare npx command fails to launch MCP servers on Windows ## Observed symptom - A Windows MCP host reports spawn npx ENOENT or EINVAL while a shell or explicit Node executable can start the server. - Observed (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

MCP Inspector automatic OAuth discovers against its local proxy

## Problem - MCP Inspector automatic OAuth discovers against its local proxy ## Observed symptom - Inspector redirects to localhost proxy /authorize or fetches metadata from the proxy rather than the target MCP/authorization server. - Observed in 1 reviewed public (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

MCP protected-resource metadata is published at the wrong path

## 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 (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

MCP OAuth metadata advertises an internal origin behind a reverse proxy

## 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 (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

MCP TypeScript OAuth token exchange targets the resource server instead of a separate authorization server

## 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 (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.