RepoPicks Radar

Updated every day around 23:30 UTC

Guides

MCP Inspector

modelcontextprotocol/inspectorReviewed by AI

Checked by RepoPicks Radar on

What is MCP Inspector?

MCP Inspector is the official tool for testing Model Context Protocol servers, the add-ons that give assistants like Claude Code or Cursor new tools. One command starts it in four shapes: a web page, a terminal interface, a scriptable command line for CI, and an experimental connection tool. You connect to a server, list what it offers, call a tool with your own parameters and read the answer, including OAuth sign-in. It is for people building or checking MCP servers: you need Node 22 or newer and the terminal; a Docker image is also published.

MCP Inspector is free and open source (Apache-2.0) and can replace Postman and Insomnia.

How easy is it to install MCP Inspector?

C · install 1 or 2 tools · Windows

  • Windows C
  • macOS C
  • Linux C

Same on all three systems: install a recent Node (the README requires ^22.23.4, ^24.22.1 or >=26.12.1) and run one command, `npx @modelcontextprotocol/inspector`, which opens the web interface. There is no installer and no binary in the 75 releases, and you still need an MCP server of your own to point it at.

MCP Inspector on GitHub

Stars
11,272on Nov 10, 2026
Downloads
—all releases
Growth
+42stars in 6 days

Stars over time

11,24011,25011,26011,27011,280 Nov 6Nov 7Nov 8Nov 9Nov 10 11,24011,25011,26011,27011,280 Nov 6Nov 8Nov 10

Facts

Runs on
Windows, macOS, Linux
You need to install
Node.js
To build from source
Node.js, Docker
Disk space
100 MB–500 MB · estimate
Accounts or keys
None
Cost
Free
License
Apache-2.0 (Permissive)
Can replace
Postman, Insomnia
Last change on GitHub
Nov 4, 2026

MCP Inspector risk signals (5)

  • Attentionsecrets can be stored unencrypted

    README warning: "The Inspector manages secrets — OAuth tokens, OAuth client secrets, and stdio `env:` values — and stores them in the OS keychain, if available, by default. On a machine with no keychain — Linux without libsecret or a Secret Service, headless and SSH sessions, Termux, and containers with a mounted volume — they are saved to `~/.mcp-inspector/secrets.json` instead, unencrypted unless you supply a key."

    AI review

  • Attentiondocker image opens the backend to the network

    Dockerfile: `ENV HOST=0.0.0.0 DANGEROUSLY_BIND_ALL_INTERFACES=true`, with the comment "Binding 0.0.0.0 is refused by default (it exposes the process-spawning backend to the network); a container is the sanctioned exception". The backend starts programs on the machine, so publishing ports 6274, 6275 or 6278 beyond your own computer hands that power to whoever can reach them.

    AI review

  • Infomixed licensing in the same repository

    LICENSE: "The MCP project is undergoing a licensing transition from the MIT License to the Apache License, Version 2.0", and "Contributions made by authors who originally licensed their work under the MIT License and who have not yet granted explicit permission to relicense remain licensed under the MIT License"; documentation is CC-BY-4.0. GitHub itself reports no single license for the repository. Both licenses are permissive, but the code is not uniformly one of them.

    AI review

  • Infotwo versions maintained in parallel

    README repo status: development happens on `v2/main`, while "The legacy v1 line lives on v1/main — security fixes only, published straight from that branch to the npm v1-latest tag". The releases list shows 2.14.0 and 1.0.4 published on the same day, so the version you get depends on the npm tag you ask for.

    AI review

  • Infowritten mostly by ai agents

    The repository documents its own process in docs/ai-software-factory.md, "MCP Inspector: Our AI Software Factory — How contributions actually happen since v2.0.0", with AGENTS.md as "the contract for changing this codebase... it applies to humans and AI agents alike" and agent skills in .claude/skills/. The README also says "External contributions are accepted as issues, not pull requests". The project balances this with a coverage gate of 90% per file and a mandatory pre-push check.

    AI review

Evidence is shown in its original language.

What Radar could not check about MCP Inspector

  • Whether a keychain is found on your machine, and therefore whether your OAuth tokens end up in a plain file
  • Whether the published npm package and Docker image are built from the commit analyzed here
  • How the experimental mcpdo daemon behaves when it is left running
  • Real disk use after npx downloads the package and its dependencies
  • Whether the web interface works in browsers other than the Chromium and Firefox the project smoke-tests

Similar projects

The RepoPicks app

Coming soon: install in 1 click with the RepoPicks app.

Before you download

See the release page on GitHub