Concurrent-client isolation probe

by textforagents.comcom.textforagents/concurrent-client-isolation-probev1.0.0

How the score works

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

  • Remote endpoint

Uptime

Checked  · every day

100%from 13 days of checks

Up without downtime on 13 of 13 days with data.

  • No downtime
  • Degraded
  • Down over 5 minutes
  • No data
  • Not checked yet

Response time

Median 1241 ms, slowest 5% 1517 ms for the handshake and the tool list, over 30 days.

1500 ms750 ms0

How far each check got

  • Reached the address 100%
  • Completed the handshake 100%
  • Listed its tools 100%

3 tools at the last answer.

Every day
DayResultChecksMedian
12 Nov (today)No downtime11261 ms
11 NovNo downtime1of 11286 ms
10 NovNo downtime1of 11248 ms
9 NovNo downtime1of 11200 ms
8 NovNo downtime1of 11202 ms
7 NovNo downtime1of 11220 ms
6 NovNo downtime1of 11189 ms
5 NovNo downtime1of 11259 ms
4 NovNo downtime1of 11517 ms
3 NovNo downtime1of 11260 ms
2 NovNo downtime1of 11230 ms
1 NovNo downtime1of 11239 ms
31 OctNo downtime11248 ms

A failure counts as down time only when a second check five minutes later fails too. How we check

Connect to the publisher's own endpoint

Run in a terminal:

claude mcp add --transport http concurrent-client-isolation-probe https://textforagents.com/products/concurrent-client-isolation-probe/mcp
For agents: the install prompt

Every step above as one Markdown text, for an assistant installing it for you.

# Install the MCP server Concurrent-client isolation probe (`com.textforagents/concurrent-client-isolation-probe`)

Its page: https://plug.directory/servers/com.textforagents/concurrent-client-isolation-probe

It runs on the publisher's servers; the client connects to its URL.

Use the section for the person's client.

## Claude Desktop

Paste into Settings › Connectors › Add custom connector:

```text
https://textforagents.com/products/concurrent-client-isolation-probe/mcp
```

## Claude Code

Run in a terminal:

```sh
claude mcp add --transport http concurrent-client-isolation-probe https://textforagents.com/products/concurrent-client-isolation-probe/mcp
```

## Cursor, Devin Desktop, LM Studio, oterm, Bob Shell, ECA, Kiro, Kiro CLI

Merge into the place for the person's client:

- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- Bob Shell: ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
- Kiro: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)
- Kiro CLI: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)

```json
{
  "mcpServers": {
    "concurrent-client-isolation-probe": {
      "url": "https://textforagents.com/products/concurrent-client-isolation-probe/mcp"
    }
  }
}
```

## VS Code

Merge into .vscode/mcp.json:

```json
{
  "servers": {
    "concurrent-client-isolation-probe": {
      "type": "http",
      "url": "https://textforagents.com/products/concurrent-client-isolation-probe/mcp"
    }
  }
}
```

## Zed

Merge into ~/.config/zed/settings.json:

```json
{
  "context_servers": {
    "concurrent-client-isolation-probe": {
      "url": "https://textforagents.com/products/concurrent-client-isolation-probe/mcp"
    }
  }
}
```

## Cline

Merge into cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):

```json
{
  "mcpServers": {
    "concurrent-client-isolation-probe": {
      "type": "streamableHttp",
      "url": "https://textforagents.com/products/concurrent-client-isolation-probe/mcp"
    }
  }
}
```

## Continue

Merge into ~/.continue/config.yaml:

```yaml
mcpServers:
  - name: "concurrent-client-isolation-probe"
    type: streamable-http
    url: "https://textforagents.com/products/concurrent-client-isolation-probe/mcp"
```

## Goose

Merge into ~/.config/goose/config.yaml:

```yaml
extensions:
  "concurrent-client-isolation-probe":
    type: streamable_http
    name: "concurrent-client-isolation-probe"
    enabled: true
    uri: "https://textforagents.com/products/concurrent-client-isolation-probe/mcp"
    headers: {}
    env_keys: []
    envs: {}
    timeout: 300
```

## Gemini CLI

Merge into ~/.gemini/settings.json:

```json
{
  "mcpServers": {
    "concurrent-client-isolation-probe": {
      "httpUrl": "https://textforagents.com/products/concurrent-client-isolation-probe/mcp"
    }
  }
}
```

## Codex

Run in a terminal:

```sh
codex mcp add concurrent-client-isolation-probe --url https://textforagents.com/products/concurrent-client-isolation-probe/mcp
```

## mcp-client-cli, TUUI, BoltAI

This server's endpoint speaks streamable HTTP, which this client's documentation does not list among its transports; use another client for it.

## Agenvoy

Merge into ~/.config/agenvoy/mcp.json:

```json
{
  "servers": {
    "concurrent-client-isolation-probe": {
      "url": "https://textforagents.com/products/concurrent-client-isolation-probe/mcp"
    }
  }
}
```

## Amp

Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):

```json
{
  "amp.mcpServers": {
    "concurrent-client-isolation-probe": {
      "url": "https://textforagents.com/products/concurrent-client-isolation-probe/mcp"
    }
  }
}
```

## AnythingLLM

Merge into anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:

```json
{
  "mcpServers": {
    "concurrent-client-isolation-probe": {
      "type": "streamable",
      "url": "https://textforagents.com/products/concurrent-client-isolation-probe/mcp"
    }
  }
}
```

## Augment Code

Merge into Augment Settings Panel – MCP section – Import from JSON (VS Code extension):

```json
{
  "mcpServers": {
    "concurrent-client-isolation-probe": {
      "type": "http",
      "url": "https://textforagents.com/products/concurrent-client-isolation-probe/mcp"
    }
  }
}
```

Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.

From the publisher's entry in the Official MCP Registry (the registry entry). Report a problem