Concurrent-client isolation probe
Server Details
Concurrent two-client overlap probe proving MCP servers do not cross-deliver tool results.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-03-26
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 3 tools
The three tools have mostly distinct actions: probe_isolation runs a probe, get_verdict retrieves the latest verdict, and verify_receipt verifies a signed receipt. get_verdict and verify_receipt could be confused by an agent because both involve signed verdict artifacts, but the retrieve-versus-verify distinction is clear enough.
All tool names follow a consistent snake_case verb_noun pattern: get_verdict, probe_isolation, verify_receipt. The naming is predictable and readable across the set.
Three tools is appropriate for a narrow server focused on running isolation probes and handling signed verdicts. Each tool has a necessary role: execute the probe, retrieve the result, and verify the receipt.
The surface covers the core lifecycle of running a probe, retrieving a verdict, and verifying a receipt. Minor gaps exist, such as no tool to list endpoints, verdicts, or probe history, but the main workflow is not blocked.
Available Tools
3 toolsget_verdictCInspect
Latest signed verdict on file for an endpoint.
Inputs: endpoint (required).
probe_isolationBInspect
Run a full concurrent-client isolation probe against an operator-authorised MCP server; returns a signed per-surface verdict.
Inputs: target (required), authorisation (required).
verify_receiptCInspect
Verify a signed verdict receipt.
Inputs: receipt (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Observed facts on public MCP servers: protocol checks, tool changes, signed evidence. No verdicts.
Pre-connection collision audit for merged MCP toolboxes, trust-graded, with signed routing receipts.
Observe MCP tools, verify repeated reads, then try bounded exact reuse for free.
Independent trust scores, tool surfaces and change history for MCP servers.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceA transparent MCP proxy that independently re-verifies tool-call claims instead of trusting them, paired with devmcp — the git/CI server it's proven against.16 PyPI1MIT
- AlicenseNot gradedqualityDmaintenanceMCP servers for real-time development monitoring and interactive pair programming.1MIT
- AlicenseNot gradedqualityDmaintenanceTwo MCP servers demonstrating tool visibility scoping and ui/update-model-context for stage magic on language models.2MIT
- AlicenseAqualityBmaintenanceCoordination protocol for parallel coding agents, built above Git. The MCP server exposes the full 17-tool lifecycle over stdio: register agents, publish intents with semantic scopes and declared operations, claim work, check for conflicts before code is written, publish ChangeSets, run trusted named verification checks, and record accepted work. Deterministic rules raise findings when two agents'18437Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.