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
Exitprobe
Overview
Description from the maker (original English)
Check whether an exit IP works for AI services: ASN, network type, risk, AI availability.
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?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"exitprobe": {
"command": "npx",
"args": [
"-y",
"@reneturcios/exitprobe",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add exitprobe -- npx -y @reneturcios/exitprobe mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"exitprobe": {
"command": "npx",
"args": [
"-y",
"@reneturcios/exitprobe",
"mcp"
]
}
}
}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.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"exitprobe": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/exitprobe",
"mcp"
]
}
}
}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 CloudCorpRecords, 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 32398 servers in this category
- Published to the registry more recently than 91% of the other 32398 servers in this category
- Basic checks equal to or better than 100% of the other 32398 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 Exitprobe 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.1.0) reached the registry 3 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, Docker on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, AI Deprecations
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
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
AI Deprecations
by aideprecations.com
AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.
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.
exitprobe
An exit IP can look perfectly ordinary and still be useless for AI services: it may sit in a datacenter range, arrive through a proxy, or carry a risk profile that providers quietly refuse. exitprobe asks ipforai.cc to profile an exit address before you find that out the hard way.
The profile it returns covers the location, the ASN, the network type (residential, ISP, datacenter, proxy or Tor), the access and routing type, a risk level, an environment score, and whether common AI services are reachable from that exit, along with a link to the full report. exitprobe adds nothing of its own to that answer: a successful call hands the upstream JSON back verbatim, exactly as ipforai.cc produced it.
The two tools:
check_my_ip— profile the exit this machine actually uses, for both its IPv4 and IPv6 addresses where present. Handy as a pre-flight check before routing work through a new connection.lookup_ip— profile any IPv4 or IPv6 address you name, so you can vet a candidate exit before anything depends on it.
A note on the lookup wire
check_my_ip is served from ipforai.cc's documented /json endpoint. For lookup_ip, the upstream documentation pins that the server calls ipforai.cc's /json and exit echo endpoints but does not pin the per-address lookup path, so this rebuild uses GET /json?ip= — a documented reconstruction, not a verified upstream contract. Because the profile JSON is returned verbatim either way, any field naming in the result is the upstream's own.
CLI
npx @reneturcios/exitprobe check_my_ipnpx @reneturcios/exitprobe lookup_ip '{"ip":"1.2.3.4"}' npx @reneturcios/exitprobe --version
check_my_ip takes no argument; lookup_ip takes one JSON argument string. Output is the tool's result text (the upstream JSON profile). Exit codes: 0 on success, 1 on a runtime error (including a validation or upstream failure), 2 on a usage error.
Failures are reported plainly: a non-2xx upstream response is ipforai error: HTTP , an unreachable upstream is ipforai unreachable, and a missing or empty ip argument is ip must be a non-empty string — checked before any request is made.
MCP server
npx -y @reneturcios/exitprobe mcpMCP client config:
{"mcpServers": { "exitprobe": { "command": "npx", "args": ["-y", "@reneturcios/exitprobe", "mcp"] } } }
Docker
docker run -i ghcr.io/cloudcorprecords/exitprobedocker run --rm ghcr.io/cloudcorprecords/exitprobe lookup_ip '{"ip":"1.2.3.4"}'
Development
npm installnpm run build # tsc -> dist/ npm test # tsx --test test/*.test.ts (fake fetch only, no network) npm run dev # run the CLI from source
License
MIT — Copyright (c) 2026 Rene Turcios