The MCP Inspector is a developer tool for testing and debugging MCP servers. It is NOT an MCP server itself. Run it with: npx @modelcontextprotocol/inspector
Is it safe?
No package registry to scan for CVEs.
No authentication — any process on your machine can connect to this server.
License not specified.
Last scanned 0 days ago.
Is it maintained?
Last commit 0 days ago. 9,310 GitHub stars.
Will it work with my client?
Transport: stdio, sse, http. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
How much context will it use?
0 tools. Token cost not measured.
What if it doesn't work?
Common issues: JSON syntax errors in config, network or firewall blocking. covers troubleshooting.
{
"mcpServers": {
"my-server": {
"env": {
"key": "value",
"key2": "value2"
},
"args": [
"build/index.js",
"arg1",
"arg2"
],
"command": "node"
},
"everything": {
"env": {
"hello": "Hello MCP!"
},
"args": [
"@modelcontextprotocol/server-everything"
],
"command": "npx"
}
}
}This server supports HTTP transport. Be the first to test it — help the community know if it works.
Last scanned 2h ago
No known vulnerabilities.
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.