Trustabl Probe

Name: Trustabl Probe
Author: trustabl

by trustablversion 0.5.0i★ –iRuns on your computer

Registry nameio.github.trustabl/agent-network-access-probe

Install

Overview

Description from the maker (original English)

Drafts a network allow list for agent tools and runs them in a network-blocked sandbox.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Download the maker’s .mcpb file

The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.

Run this in your terminal

claude mcp add agent-network-access-probe -- npx -y @trustabl/agent-network-access-probe

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account trustabl, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32466 servers in this category
Published to the registry more recently than 76% of the other 32466 servers in this category
Basic checks equal to or better than 100% of the other 32466 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Trustabl Probe safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.5.0) reached the registry 10 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, MCPB on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, HotCodePush

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

HotCodePush

by hotcodepush-team

Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Trustabl Probe MCP server

Gives your coding agent Trustabl Probe: it drafts a network allow list for an agent tool and runs the tool in a network-blocked sandbox to catch problems that only show up at runtime. Every finding comes with a fix hint, and your agent applies the fixes, so no model or API key is needed.

Tools

Tool	What it does	Changes anything?
`probe_check_setup`	Reports whether the Probe binary, Docker and the sandbox images are ready, which languages can run in the sandbox, and the exact command to fix each missing piece.	No
`probe_install`	Downloads the Probe binary (checksum-verified) and pulls the sandbox images. For Docker, OpenShell or Python it only returns the command to run, with its caveats.	Yes, see below
`probe_scan`	Scans a tool directory and returns a readiness score, the draft network allow list, and findings worst-first with fix hints.	Writes four report files into the scanned directory

Static and sandbox

Static reads the code and flags problems such as missing timeouts, hardcoded credentials or unfiltered tool output. It also drafts the network allow list (an OpenShell network policy) from the code. It always runs and needs nothing extra.
Sandbox also runs the tool with its network blocked, catching crashes, missing dependencies and blocked connection attempts. It needs Docker (or NVIDIA OpenShell). With sandbox: "auto", the default, it runs whenever a runner is ready. Tools that look destructive (payments, deletes, network writes) are not run unless you pass allow_write_tools: true.

Docker covers Python, JavaScript/TypeScript, Go and Ruby; the OpenShell image runs Python and Node. Shell scripts are always analyzed statically only.

Install

Requires Node.js 18 or later. Docker is optional and enables the sandbox.

The server is the npm package @trustabl/agent-network-access-probe, and every Probe release also attaches it as trustabl-agent-network-access-probe- .tgz and .mcpb.

Cursor (.cursor/mcp.json):

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

Claude Code:

claude mcp add agent-network-access-probe -- npx -y @trustabl/agent-network-access-probe

Claude Desktop: download trustabl-agent-network-access-probe- .mcpb from the release and open it to install. Or use the same command and args as the Cursor example under mcpServers in claude_desktop_config.json.

To pin one release instead of following the latest, replace the package name in args with that release's .tgz URL.

Then ask your agent to run probe_check_setup.

What it changes on your machine

Downloads the Probe binary from the same release as the server into ~/.trustabl-probe/ /, after checking it against the release checksums.txt. A mismatch is a hard failure.
Pulls the sandbox images (python:3-slim, node:20-slim, golang:1.25-alpine, ruby:3-slim) when you run probe_install, or on the first sandbox run.
Writes network_policies.draft.yaml, probe.findings.json, probe.profile.json and autofix-attestation.json into the scanned directory.
Never installs Docker, OpenShell or Python itself. It returns the command, and your agent should ask you before running it. Docker Desktop needs admin rights, may need a restart on Windows, and needs a paid subscription for larger companies.

Privacy Policy

Trustabl's privacy policy: https://trustabl.ai/privacy/

What this server does with your data:

Collection: none. It sends no telemetry and makes no model call.
Your code: it is read and analyzed on your machine and never uploaded. Attestation signing is turned off, so nothing goes to a transparency log.
Network access: only GitHub (to download the Probe release), Docker Hub (for the sandbox images) and, when a Python tool declares dependencies, PyPI to install them before the sandbox run. The tool under test runs with its network blocked.
Storage: the Probe binary is cached in ~/.trustabl-probe/, sandbox results are cached in your user cache folder under trustabl-probe/results, and the four report files are written into the scanned directory. Delete any of them at any time.
Third parties: nothing is shared with Trustabl or anyone else.
Contact: https://github.com/trustabl/agent-network-access-probe/issues

Settings

Variable	Default	Purpose
`PROBE_VERSION`	the release the server came with	Probe release to use instead, e.g. `v0.2.3` or `latest`. Needs v0.2.3 or later.
`PROBE_BIN`		Path to a local Probe build; skips the download
`GITHUB_TOKEN`		Only to avoid GitHub's anonymous rate limit when `PROBE_VERSION` is `latest`

Development

From mcp/:

cd server && npm ci && npm run build   # bundles to dist/index.js, which is committed

node test/smoke.mjs # handshake, tools/list, setup check SMOKE_SCAN=1 node test/smoke.mjs # also a static scan of test/fixture with the released Probe PROBE_BIN=/path/to/autofix node test/smoke.mjs # the same scan with a local Probe build

A checkout has version 0.0.0 and uses the latest Probe release. The release workflow sets the real version when it packs the server.

License

Apache-2.0, like Probe.

Trustabl Probe

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

HotCodePush

README from the maker

Trustabl Probe MCP server

Tools

Static and sandbox

Install

What it changes on your machine

Privacy Policy

Settings

Development

License