modelcontextprotocol/inspector

MCPcommunity
modelcontextprotocolNOASSERTIONUpdated 3mo agoGitHub

Visual testing tool for MCP servers

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…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
10kGitHub stars
1kForks
3mo agoLast update
Package
Authormodelcontextprotocol
LicenseNOASSERTION
Sourcegithub
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface37 tools · none privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

37 tools · none privileged
Statically extracted from the published packagevHEAD · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

echoNo description published

This tool published no description. Forge does not invent one.

addNo description published

This tool published no description. Forge does not invent one.

get-sumNo description published

This tool published no description. Forge does not invent one.

get-annotated-messageNo description published

This tool published no description. Forge does not invent one.

simple-promptNo description published

This tool published no description. Forge does not invent one.

args-promptNo description published

This tool published no description. Forge does not invent one.

test-promptNo description published

This tool published no description. Forge does not invent one.

myToolNo description published

This tool published no description. Forge does not invent one.

weatherAppNo description published

This tool published no description. Forge does not invent one.

testAppNo description published

This tool published no description. Forge does not invent one.

regularToolNo description published

This tool published no description. Forge does not invent one.

calendarAppNo description published

This tool published no description. Forge does not invent one.

fieldsAppNo description published

This tool published no description. Forge does not invent one.

noDescriptionAppNo description published

This tool published no description. Forge does not invent one.

complexAppNo description published

This tool published no description. Forge does not invent one.

nullableAppNo description published

This tool published no description. Forge does not invent one.

noFieldsAppNo description published

This tool published no description. Forge does not invent one.

prefilledAppNo description published

This tool published no description. Forge does not invent one.

manualAppNo description published

This tool published no description. Forge does not invent one.

paramsAppNo description published

This tool published no description. Forge does not invent one.

failingAppNo description published

This tool published no description. Forge does not invent one.

appANo description published

This tool published no description. Forge does not invent one.

appBNo description published

This tool published no description. Forge does not invent one.

tool1No description published

This tool published no description. Forge does not invent one.

tool3No description published

This tool published no description. Forge does not invent one.

tool2No description published

This tool published no description. Forge does not invent one.

tool4No description published

This tool published no description. Forge does not invent one.

testToolNo description published

This tool published no description. Forge does not invent one.

weatherToolNo description published

This tool published no description. Forge does not invent one.

metaToolNo description published

This tool published no description. Forge does not invent one.

enumToolNo description published

This tool published no description. Forge does not invent one.

stringToolNo description published

This tool published no description. Forge does not invent one.

jsonToolNo description published

This tool published no description. Forge does not invent one.

simpleToolNo description published

This tool published no description. Forge does not invent one.

noOutputSchemaNo description published

This tool published no description. Forge does not invent one.

complexOutputSchemaNo description published

This tool published no description. Forge does not invent one.

invalidSchemaToolNo description published

This tool published no description. Forge does not invent one.

0 of 37 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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…

Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.