// MCP SERVER RECORD

Mcp Inspector

Canonical
NPM@fre4x/mcp-inspector
DRisk gradehigh blast radius
Catalogue entry updated 1 days ago
Auth postureNot probedno remote endpoint probed yet
Tools102 Execute · 1 Write · 7 Read
Worst categoryExecutegrade tracks the peak, not the average
Capability mix
Execute 2Write 1Read 7
What it can reach
Ingests untrusted inputTouches secretsReaches networkRuns codeTouches filesChanges permissionsSends external commsPersistsDeletes dataMoves money
Exfiltration pathReads content an attacker can plant and can send data outward — a prompt-injection-to-exfiltration route.
Tools 10
inspector_call_toolExecuteCriticalinspector_connectExecuteHighinspector_disconnectWriteMediuminspector_get_promptReadLowinspector_list_promptsReadLow
View all 10 tools
inspector_list_resource_templatesReadLowinspector_list_resourcesReadLowinspector_list_sessionsReadLowinspector_list_toolsReadLowinspector_read_resourceReadMedium
These definitions cost 1,097 tokens of context →
Change history
No changes recorded since first scan. Watched servers surface a diff within the hour.
Recommended policy
inspector_call_toolrequire approval
inspector_disconnectrate limit
Read-only toolsallow
Full policy breakdown with enforcement rules →
// RUNNING THIS SERVER
DIRECT INSTALL npx -y @fre4x/mcp-inspector

Installed this way, nothing enforces the recommended policy above — calls run exactly as the agent makes them.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.