MCP Client Compatibility Probe
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PROBE_TRACE | No | Path to the trace log file (NDJSON). Defaults to /tmp/mcp-probe.ndjson. | /tmp/mcp-probe.ndjson |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echo_metaA | Returns the received arguments and MCP request metadata. Use this first to inspect protocolVersion, clientInfo, and clientCapabilities. |
| structured_resultB | Returns both text content and structuredContent conforming to outputSchema. |
| create_handleA | Creates an explicit short-lived probe handle to test stateless multi-call tool design. |
| use_handleC | Uses a handle returned by create_handle. Unknown handles return a tool execution error. |
| needs_form_inputA | Returns resultType input_required until the client retries with inputResponses. This tests MRTR and elicitation form mode. |
| tool_errorA | Always returns a tool execution error via isError true, not a JSON-RPC protocol error. |
| resource_link_resultC | Returns a resource_link content item pointing at a probe resource. |
| searchA | ChatGPT-compatible read-only search stub. Returns result IDs, titles, and URLs. Use fetch to retrieve full text. |
| fetchA | ChatGPT-compatible read-only fetch stub. Retrieves full text for an ID returned by search. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| probe_summary | Prompt template that asks the model to summarize observed MCP client behavior. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| overview | Short overview resource exposed by the probe server. |
| client-observation | Checklist for interpreting the probe trace log. |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/kascada/mcp-client-compat-probe'
If you have feedback or need assistance with the MCP directory API, please join our Discord server