# modelcontextprotocol/inspector

Visual testing tool for MCP servers

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Author:** modelcontextprotocol
- **License:** NOASSERTION
- **Source:** https://github.com/modelcontextprotocol/inspector

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 113 days — stale; the grade is a claim about the present made from dated evidence

## Security scan

- **Status:** clean
- **Scanned:** 2026-06-14T11:07:48.272Z
- **Version scanned:** HEAD
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

37 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `echo`
- `add`
- `get-sum`
- `get-annotated-message`
- `simple-prompt`
- `args-prompt`
- `test-prompt`
- `myTool`
- `weatherApp`
- `testApp`
- `regularTool`
- `calendarApp`
- `fieldsApp`
- `noDescriptionApp`
- `complexApp`
- `nullableApp`
- `noFieldsApp`
- `prefilledApp`
- `manualApp`
- `paramsApp`
- `failingApp`
- `appA`
- `appB`
- `tool1`
- `tool3`
- `tool2`
- `tool4`
- `testTool`
- `weatherTool`
- `metaTool`
- `enumTool`
- `stringTool`
- `jsonTool`
- `simpleTool`
- `noOutputSchema`
- `complexOutputSchema`
- `invalidSchemaTool`

## Install

This entry has no npm package and no hosted endpoint, so there is nothing for an MCP client to launch or connect to. It is indexed as source only.

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: read-only tool surface.
- Floor 3, ceiling 33 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/modelcontextprotocol%2Finspector
- Install plan: https://forgeregistry.com/api/v1/packages/modelcontextprotocol%2Finspector/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/modelcontextprotocol%2Finspector
- HTML page: https://forgeregistry.com/registry/modelcontextprotocol%2Finspector
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.