跳到主要内容
Supermarket
返回能力市场
MCP Server
design
NOASSERTION

inspector

Deterministic testing tools for MCP servers

modelcontextprotocolmodelcontextprotocol
88/ 100

公开评测 · 综合采用结论

证据充分,整体质量与安全表现优秀

查看评测依据 查找我项目的报告基于公开项目证据,非安全认证或安装推荐
11.3kstars
1.6kforks
最近更新 5天前
评测生成时间(北京时间)
本报告引擎
v3.10.0
当前引擎
v3.17.3

本报告与当前引擎使用不同规则;原分数不会自动更新,不同版本的分数不宜直接对比。

重新评测此项目

进入后确认来源与额度,提交才会创建任务。

代码版本未记录或记录无效,无法核对本报告的 commit 与送评文本;不会用当前项目代码回填历史记录。

Evaluation report

综合采用结论

88
A
满分 100 · 静态采用参考
值得推荐低风险
决策摘要

证据充分,整体质量与安全表现优秀

100%
高置信度
90
文档
100
安全
76
质量
100
活跃
70
采用
  • 基础评测完成+25/25确定性评分与静态安全扫描已完成
  • README 有效证据+25/2565,557 个去重后的有效字符
  • 独立证据来源+20/205 类非重复证据,重复文件不叠加
  • 仓库元数据+10/10已取得仓库状态与采用数据
  • 活跃记录+5/5已取得最近提交时间
  • AI 复核+15/15已完成结构化 AI 证据复核

本报告评了什么

综合分用于静态采用筛选,不是任务成功率,也不代表使用 Skill 后的能力提升。

静态检查范围
记录 8 个文件 · 114,358 字符
只检查采集到的受限文本与已知风险模式;未读取的脚本、依赖和运行环境不在结论内。
AI 内容复核
已使用
复核送评文本的说明和设计,不是安装测试或实际任务执行。记录缺失时不推断已使用或未使用。
真实任务效果
本报告未提供实测证据
没有使用/不使用 Skill 的任务对照、重复运行或耗时与 token 成本结果。采用前仍需在隔离环境验证自己的任务。

脚本引用覆盖

脚本引用覆盖记录不可得;不推断没有引用或已经检查。

How it works · 架构图

MCP Inspector 架构概览

README 描述了多个客户端(web/cli/tui)共享 core 模块,并通过 launcher 分发,适合用架构图展示组件关系。

AI 提取 · 证据约束

左右滑动查看完整图示

MCP Inspector 架构概览README 描述了多个客户端(web/cli/tui)共享 core 模块,并通过 launcher 分发,适合用架构图展示组件关系。分发分发分发使用使用使用启动器入口Web 客户端浏览器界面CLI 客户端命令行TUI 客户端终端界面核心模块共享代码
图示依据
  • • README 中 'Project layout' 章节:'clients/launcher/ # Shared launcher — provides the mcp-inspector bin, dispatches to web/cli/tui'
  • • README 中 'Project layout' 章节:'core/ # Shared code consumed via the @inspector/core alias'
  • • README 中 'Setup' 章节:'npx @modelcontextprotocol/inspector --cli' 等命令
五维表现
MCP Inspector 提供 Web/CLI/TUI 三种方式,解决 MCP 服务器调试的真实需求,文档详尽,但安装示例仅限 npx,缺少本地构建与配置示例,且未明确列出所有限制。
质量证据
  • README 中 'Setup' 章节:'Requires Node >=22.19.0' 和 'npm install' 命令
  • README 中 'Project layout' 章节:列出 clients/web, cli, tui, launcher 等目录结构
  • README 中 'Testing & the quality gate' 章节:详细列出 validate, coverage, smoke 等脚本
  • README 中 'Publishing' 章节:说明单包发布和打包不变量
  • README 中 'MCP Apps' 章节:提供 mcp-app-http.json 演示服务器和 Apps 标签页使用说明
采用建议
优势
  • 有效 README
  • 安装或接入步骤
  • 可执行示例
  • 输入、参数或工具说明
  • 未发现已知高风险模式
关注点
  • 缺少问题与用途描述
  • 安装示例仅展示 npx 命令,缺少本地构建或配置示例
  • 未明确列出所有限制或不支持的功能
  • 文档中部分内容(如测试脚本表)过于冗长,可能影响快速上手
  • 缺少错误处理或排障的专门章节
适合

MCP 服务器开发者需要调试和验证工具、需要在 CI 中自动化测试 MCP 服务器的团队、需要交互式终端界面的开发者、需要审查 MCP App 的开发者

不建议直接用于

非 MCP 相关项目的调试、需要图形化界面但不想使用 Web 浏览器的场景(TUI 可能不够直观)

也有自己的公开项目?先免登录查已有报告;没有报告时,可保留地址继续登录评测。

查找我项目的报告 →
文档证据
90/100
问题与用途描述10 分
有效 README12 分
安装或接入步骤14 分
可执行示例16 分
输入、参数或工具说明11 分
输出或结果说明9 分
限制、权限或边界12 分
错误处理或排障8 分
许可证信息5 分
结构化章节3 分
安全证据
低风险
未发现已知高风险模式

静态扫描不是安全保证,生产接入前仍应人工复核权限和数据边界。

优先改进清单
  1. 01补充问题与用途描述
方法、证据与局限展开
数据来源

GitHub Repository API

扫描范围

8 个文件 · 114,358 字符

评测引擎

v3.10.0 · AI 内容复核:已使用(deepseek-chat)

局限
  • 静态评测不会安装或执行项目代码
  • 安全扫描基于高信号文件与已知模式,不能替代人工审计
  • 流行度只反映采用程度,不代表安全或工程质量

30 天热度趋势

README

MCP Inspector

A developer tool for inspecting Model Context Protocol (MCP) servers. It ships as a single package, @modelcontextprotocol/inspector, that provides four ways to inspect a server:

  • Web — a Vite + React + Mantine single-page app with a Node backend.
  • CLI — a scriptable command-line client for automation, CI, and fast agent feedback loops.
  • TUI — an interactive terminal UI built with Ink.
  • mcpdo (experimental) — a connection CLI: connect once, then run many commands against the named connection through an implicit local daemon. See clients/mcpdo.

The first three run through one global mcp-inspector binary; mcpdo is a second binary in the same package:

npx @modelcontextprotocol/inspector                   # web UI (default)
npx @modelcontextprotocol/inspector --cli             # CLI
npx @modelcontextprotocol/inspector --tui             # TUI
npx -p @modelcontextprotocol/inspector mcpdo --help   # mcpdo

[!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. See Where secrets are stored for how to get a keychain back, encrypt the file, or keep secrets in memory only.

Upgrading from v1? Read the v1 → v2 migration guide — CLI flags, the new --config vs. --catalog split, the Node engine bump, and what no longer ships.

Repo status. This is the v2 line of the Inspector. Active development happens on v2/main (the develop branch — all v2 PRs target it), which is merged into main at milestone releases; main is the default branch and holds the latest released v2, published to the npm latest tag. The legacy v1 line lives on v1/main — security fixes only, published straight from that branch to the npm v1-latest tag (npx @modelcontextprotocol/inspector@v1-latest). See AGENTS.md for branch/board conventions.

Quick start (development)

Requires Node >=22.19.0.

npm install          # at the repo root; postinstall cascades into every client
npm run build        # web → cli → tui → launcher

For day-to-day web iteration, run Vite directly — fast HMR, no launcher build needed:

cd clients/web && npm run dev

The launcher-driven scripts run the built launcher, so build first:

npm run web        # prod web launcher against clients/web/dist
npm run web:dev    # web launcher in --dev mode (Vite)

v2 is not an npm workspace — each client under clients/* keeps its own package.json and node_modules, and shared code lives in core/, consumed via a @inspector/core build-time alias. Every runtime dependency core/ imports is declared once, in the repo-root package.json, and each client declares only what that client alone consumes — its UI stack, its bundler-inlined packages, its dev tooling — which leaves clients/cli and clients/launcher with no runtime dependencies of their own. What that means for adding a dependency (root vs. client, dependencies vs. devDependencies, and the bundler external lists) is in the local-dev skill.

Project layout

inspector/
├── clients/
│   ├── web/          Web client (Vite + React + Mantine). src/ = browser app; server/ = Node backend
│   ├── cli/          CLI client (tsdown bundle, @inspector/core alias)
│   ├── mcpdo/   Experimental connection CLI (`mcpdo` bin) — bundled into the
│   │                 published package; see clients/mcpdo/README.md
│   ├── tui/          TUI client (Ink + React, tsdown bundle)
│   └── launcher/     Shared launcher — provides the `mcp-inspector` bin, dispatches to web/cli/tui
├── core/             Shared code consumed via the `@inspector/core` alias (no package.json)
├── test-servers/     Composable MCP test servers + fixtures used by integration and smoke tests
├── scripts/          Root build/verify tooling (install cascade, smokes, the verify:* guards),
│                     repo automation run from CI (the dependency, Dependabot-alert and SDK sweeps),
│                     maintainer-workflow helpers (the pr:*, board:*, advisory:*,
│                     release:notes, release:tag and action:resolve-pin aliases)
│                     and the Docker image's HEALTHCHECK probe
├── docs/             Task-oriented guides — see below
├── specification/    Design/build specifications
├── skills/           End-user agent skills (e.g. skills/mcpdo teaches an agent to
│                     drive the `mcpdo` CLI) — distinct from .claude/skills/,
│                     which holds this repo's own procedures
├── .claude/skills/   Agent skills: the repo's procedures, invokable by name
├── AGENTS.md         Contribution rules for agents AND humans
└── README.md         You are here

Each client has its own README with client-specific detail: web · cli · mcpdo · tui · launcher.

Documentation

GuideCovers
ArchitectureThe @inspector/core shared package, and the web client's "dumb components" + Storybook approach
Testing and the quality gateWhat each validate / coverage / smoke / verify:* script covers, the GitHub-CI-vs-local-gate split, and the supported browsers
Writing a skillHow to write a skill description that actually fires, and eval cases that measure it — the case shapes that work, and the tuning loop
Test serversThe composable test servers and the showcase config for every feature — what to run, what to click, and what the broken build did
PublishingWhat ships in the tarball, the packaging invariants, and pack:verify
Migrating from tsup to tsdownWhy the client bundles moved to tsdown, the option mapping, the gotchas that don't fail a build, and what each client's migration measured
Serving the web UI over HTTPSINSPECTOR_TLS_KEY_PATH / INSPECTOR_TLS_CERT_PATH, a trusted local mkcert setup, custom hostnames and ALLOWED_ORIGINS, and NODE_EXTRA_CA_CERTS for outbound private-CA servers
DockerRunning the container image — ports, volumes, and making secrets durable in a container
Where secrets are storedHow the secret store is chosen on every runtime — OS keychain, secrets.json or memory — plus file encryption, locking, and moving back to a keychain
Migrating from v1 to v2CLI flag mapping, --config vs. --catalog, the Node engine bump, env-var renames
Environment variablesEvery variable that changes runtime behavior — auth, ports, storage, the secret store, logging, proxies — plus the Node TLS variables for a self-signed server
MCP server configurationWhich server(s) the Inspector connects to, and the config file format
Reviewing an MCP AppThe CLI-first → one-shot-web recipe for automated App-tool review
Smoke-testing an MCP serverThe connect → list → call → assert workflow for a shell or CI job: --format json + jq, the exit-code map, and keeping OAuth non-interactive
Retroactive DCO signoffsThe ten commits that merged without a Signed-off-by: while no DCO check ran, and each author's signed-off certification of them
Launcher and config consolidationWhy the launcher runs a client in-process rather than spawning it
Roadmap, Aug 2026 → Feb 2027The six-month plan: spec-following work aligned to the published MCP roadmap, official extension support, and the experience work we choose
MCP Inspector: Our AI Software FactoryHow contributions actually happen since v2.0.0 — issue-driven work end to end, the rules/skills split, the sweeps that replaced Dependabot, the quality gate, and where it's headed

Testing and the quality gate

Each client self-validates from its own folder; the root scripts chain them. There is no aggregate root test script.

npm run validate     # fast inner loop: format:check + lint + typecheck + build + unit tests
npm run coverage     # the per-file ≥90% gate (lines/statements/functions/branches)
npm run local:gate   # MANDATORY before pushing — every GitHub CI check, plus one local-only one

npm run local:gate chains every check below, plus the smokes and the Storybook tests. Testing and the quality gate owns the stage list and says what each one covers and why one is local-only; AGENTS.md holds the testing rules themselves.

Contributing — AGENTS.md, CLAUDE.md, and the skills

AGENTS.md is the contract for changing this codebase, and it applies to humans and AI agents alike. It is not agent-only boilerplate — it holds the project's real rules: the version/label conventions, the TypeScript and Mantine/React standards, the testing and coverage requirements, and the mandatory pre-push gate. Read it before making changes, and keep it up to date when you change structure, tooling, or rules.

The repo's procedures — multi-step recipes with commands and live IDs — live in .claude/skills/ instead, one directory per procedure, so they are loaded only when the task calls for them. They are ordinary committed Markdown: an agent that doesn't understand skills can read them, and AGENTS.md carries an index of what exists. Claude Code users invoke one by name (/release, /issue-triage, …).

CLAUDE.md is the entry point Claude Code loads automatically; it includes AGENTS.md, so agents and humans work from the same source of truth. If you use a different agent that reads AGENTS.md, you get the same rules.

A key rule worth surfacing here: all work is issue-driven. Before starting, find or create a tracking issue on the v2 project board; open PRs against v2/main with Closes #<issue>. External contributions are accepted as issues, not pull requests — see CONTRIBUTING.md.

License

See LICENSE. The MCP project is transitioning from the MIT License to Apache-2.0: new code contributions are licensed under Apache-2.0, documentation (excluding specifications) under CC-BY-4.0, and contributions whose authors originally licensed them under MIT and have not granted relicensing consent remain under MIT. The file carries the full Apache-2.0 and MIT texts and links the CC-BY-4.0 legal code.