Server-side application for the Model Context Protocol inspector
The MCP inspector is a developer tool for testing and debugging MCP servers. The MCP Inspector consists of two main components that work together: MCP Inspector Client (MCPI): A React-based web UI that provides an interactive interface for testing and debugging MCP servers MCP Proxy (MCPP): A Node.js server that acts as a protocol bridge, connecting the web UI to MCP servers via various transport…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 2 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
The MCP inspector is a developer tool for testing and debugging MCP servers. The MCP Inspector consists of two main components that work together: MCP Inspector Client (MCPI): A React-based web UI that provides an interactive interface for testing and debugging MCP servers MCP Proxy (MCPP): A Node.js server that acts as a protocol bridge, connecting the web UI to MCP servers via various transport methods (stdio, SSE, streamable-http) Note that the proxy is not a network proxy for intercepting…
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.