Skip to main content
Glama

Concurrent-client isolation probe

Server Details

Concurrent two-client overlap probe proving MCP servers do not cross-deliver tool results.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-03-26
URL
ChatGPT
–
Claude
–

TDQS

B3.1/5.0

Scored across 3 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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 tools
get_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

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      A 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 PyPI
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Coordination 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'
      18
      437
      Apache 2.0
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources