# Trustabl Probe MCP server

> Draft a least-privilege network allow list for agent tools by running them in a network-blocked sandbox and scanning their code.

- Listing: https://mcp.tc/i/trustabl-probe
- Connect: this is a local (stdio) server; install it on your machine (see Install). The listing link is a page, not an MCP endpoint.
- Type: local (stdio)
- Auth: no API key needed
- Category: [Security & Compliance](https://mcp.tc/c/security)
- Vendor: Trustabl
- Homepage: <https://trustabl.ai>
- Repository: <https://github.com/trustabl/agent-network-access-probe/tree/HEAD/mcp>
- Package: npm `@trustabl/agent-network-access-probe`

## About

Trustabl Probe runs an agent tool in an isolated OpenShell or Docker sandbox, records the network destinations it reaches, and generates a least-privilege OpenShell network policy draft from that evidence. Static analysis also flags hardcoded credentials, missing timeouts and unauthorized network calls, with optional generated fixes. Sessions can be attested with Sigstore keyless signing.

It runs locally over stdio as an npm package (npx) or an MCP bundle, so source code stays on your machine. It needs Docker or OpenShell as the sandbox runner. No model key is needed for scanning; an OpenAI-compatible LLM endpoint is only used for generated fixes.

## What it can do

- Run agent tools in a network-blocked sandbox and observe reached destinations
- Generate a least-privilege OpenShell network policy draft
- Flag hardcoded credentials and missing timeouts via static analysis
- Apply custom allow and deny lists to the generated policy
- Produce optional Sigstore-signed attestations of a run
- Skip tools with side effects unless explicitly allowed

## Example prompts

- "Scan ./my-tool and draft a network policy from the destinations it reaches"
- "Check what Probe needs installed on this machine, then run it on my agent tool"
- "Run Probe with the Docker runner and show the findings for my tool directory"
- "Generate a policy for my tool but flag anything not on my allow list"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport stdio trustabl-probe -- npx -y @trustabl/agent-network-access-probe
```

2. Start Claude Code and type `/mcp`. **trustabl-probe** should show as connected.

Add `--scope user` to make it available in every project.

### Claude Desktop

1. Open **Settings → Developer → Edit Config**. It opens `claude_desktop_config.json`. Add:

`claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "trustabl-probe": {
      "command": "npx",
      "args": [
        "-y",
        "@trustabl/agent-network-access-probe"
      ]
    }
  }
}
```

2. Save the file and restart Claude Desktop.

Needs Node.js on your computer. The file lives in `~/Library/Application Support/Claude/` on macOS and `%APPDATA%\Claude\` on Windows.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=trustabl-probe&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIkB0cnVzdGFibC9hZ2VudC1uZXR3b3JrLWFjY2Vzcy1wcm9iZSJdfQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "trustabl-probe": {
      "command": "npx",
      "args": [
        "-y",
        "@trustabl/agent-network-access-probe"
      ]
    }
  }
}
```

Needs Node.js on your computer.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=trustabl-probe&config=%7B%22type%22%3A%22stdio%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22%40trustabl%2Fagent-network-access-probe%22%5D%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"trustabl-probe","type":"stdio","command":"npx","args":["-y","@trustabl/agent-network-access-probe"]}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "trustabl-probe": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@trustabl/agent-network-access-probe"
      ]
    }
  }
}
```

Needs Node.js on your computer.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "trustabl-probe": {
      "command": "npx",
      "args": [
        "-y",
        "@trustabl/agent-network-access-probe"
      ]
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf.

### Codex

```bash
codex mcp add trustabl-probe -- npx -y @trustabl/agent-network-access-probe
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.trustabl-probe]
command = "npx"
args = ["-y", "@trustabl/agent-network-access-probe"]
```

Needs Node.js on your computer.

### Gemini CLI

```bash
gemini mcp add trustabl-probe npx -- -y @trustabl/agent-network-access-probe
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients that start local servers accept this shape:

```json
{
  "mcpServers": {
    "trustabl-probe": {
      "command": "npx",
      "args": [
        "-y",
        "@trustabl/agent-network-access-probe"
      ]
    }
  }
}
```

Zed puts servers under `context_servers` in its settings, with the same `command`, `args` and `env` fields.

Needs Node.js on your computer.

## Recent changes

- 2026-11-01 05:21 UTC: Tracking started: version 0.5.0. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/trustabl-probe#history (Atom feed: https://mcp.tc/i/trustabl-probe/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 0.5.0
- Last checked: 2026-11-01
- Listed: 2026-11-01
- Updated: 2026-11-01

---
Source: https://mcp.tc/i/trustabl-probe (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
