Audit a live MCP server
inspect_serverAudit an MCP server's tools for poisoned descriptions, destructive tools missing destructiveHint, token cost, and changes since last inspection by starting it via stdio command or HTTP.
Instructions
Start an MCP server (stdio command, or a Streamable HTTP url), read its tool list, and audit it: poisoned tool descriptions, destructive tools without a destructiveHint, context cost in tokens, and tools that changed since the last inspection.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "inspect_server"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Streamable HTTP endpoint, instead of command | |
| args | No | Arguments, e.g. ["-y", "some-mcp-server"] | |
| command | No | Executable for a stdio server, e.g. npx |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tools | No | ||
| server | Yes | ||
| verdict | Yes | ||
| findings | No | ||
| contextTokens | No |