MCProbe
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| probe_connectA | Open a connection to an MCP target server (stdio or HTTP) and return a connectionId plus the server's name, version, capabilities, and counts. |
| probe_lintA | Run the lint rules over the target's tool schemas and return a list of findings with stable codes, severities, locations, and fix hints. |
| probe_fuzzA | Generate one valid and several malformed inputs per target tool, call each, and record the outcome (ok, toolError, protocolCrash), whether malformed inputs were silently accepted, and call latency. Tools annotated destructiveHint:true are skipped by default (set fuzzDestructive to include them). Returns a coverage summary of which tools were fuzzed vs skipped. |
| probe_reportA | Run introspect + lint (and fuzz when requested) against the target, score the result on four dimensions, and return a Markdown report with the overall score, letter grade, per-dimension breakdown, findings, and fuzz table. |
| probe_listA | Enumerate the target's tools (name, description, input schema) using the default or a specific connection. |
| probe_disconnectA | Close a single connection (by id) or all connections if id is omitted. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a distinct purpose: connect, lint, fuzz, report, list, disconnect. No overlap or ambiguity in their functions.
All tools follow the consistent verb_noun pattern with 'probe_' prefix (e.g., probe_connect, probe_lint), ensuring predictability.
Six tools cover the necessary operations for probing MCP servers (connect, list, lint, fuzz, report, disconnect) without being excessive or insufficient.
The tool set covers the full lifecycle: connection, introspection (list, report), linting, fuzzing, and disconnection. No obvious gaps for the stated domain.