MCP Dock Guides
Inspect an MCP server before enabling it
The Inspector is a way to observe a server’s declared capabilities and test a narrow request. It is not a substitute for reviewing what the server command can do on your machine.
Start with declared capabilities
Check the server’s tools, resources, and prompts before calling anything. Tool names and descriptions show the intended interface; the command, package source, and permission model determine what can actually happen when a tool executes.
Test the smallest safe operation
Use a non-mutating request first, such as listing available resources or reading public metadata. Avoid entering credentials, uploading files, triggering purchases, changing remote records, or invoking destructive commands until the server and target system are understood.
Use history for diagnosis, not secret storage
Request history can reveal malformed parameters, timeout patterns, or unexpected responses. Redact secrets and personal data before sharing a diagnostic report. If a server needs privileged access, make the authorization decision at the operating-system or service-account boundary instead of treating a successful Inspector request as proof of safety.