World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 102 tools.
Description from the maker (original English)
Check whether an exit IP works for AI services: ASN, network type, risk, AI availability.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
Passed 2/2 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
One time only; it works for every server that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"exitprobe": {
"command": "npx",
"args": [
"-y",
"@reneturcios/exitprobe",
"mcp"
]
}
}
}Use Exitprobe and tell me what you can do for me, then show me one thing✓ If Claude says it is using Exitprobe or shows a Exitprobe tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Exitprobe yet
Exitprobe runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Exitprobe
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add exitprobe -- npx -y @reneturcios/exitprobe mcpYou should see Exitprobe listed as connected
Use Exitprobe and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Exitprobe or shows a Exitprobe tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Use Exitprobe and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Exitprobe or shows a Exitprobe tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Use Exitprobe and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Exitprobe or shows a Exitprobe tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add exitprobe -- npx -y @reneturcios/exitprobe mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"exitprobe": {
"command": "npx",
"args": [
"-y",
"@reneturcios/exitprobe",
"mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"exitprobe": {
"command": "npx",
"args": [
"-y",
"@reneturcios/exitprobe",
"mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"exitprobe": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/exitprobe",
"mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
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 11, 2026
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
Code last changed 8 days ago
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 2 of 2 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed 8 days ago, and the latest version (0.1.0) reached the registry 7 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: World Monitor, Claude Flow, Tldraw
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 102 tools.
AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.
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.
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.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.
npx @reneturcios/exitprobe check_my_ip
npx @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.
npx -y @reneturcios/exitprobe mcp
MCP client config:
{
"mcpServers": { "exitprobe": { "command": "npx", "args": ["-y", "@reneturcios/exitprobe", "mcp"] } } }
docker run -i ghcr.io/cloudcorprecords/exitprobe
docker run --rm ghcr.io/cloudcorprecords/exitprobe lookup_ip '{"ip":"1.2.3.4"}'
npm install
npm run build # tsc -> dist/ npm test # tsx --test test/*.test.ts (fake fetch only, no network) npm run dev # run the CLI from source
MIT — Copyright (c) 2026 Rene Turcios