IP for AI

cc.ipforaiPublished by ipforai.ccv0.1.0Updated Oct 24, 2026

Check if your exit IP works for ChatGPT, Claude, Gemini: ASN, proxy/IDC type, risk, AI availability

Overview

AI-generated overview

A local MCP server that lets an assistant check whether a machine's exit IP is suitable for AI services such as ChatGPT, Claude and Gemini.

What you can do
Check the current machine's IPv4 or IPv6 exit IP and get a profile of it, including location, ASN and network type (residential, ISP, datacenter, proxy or Tor). Look up the same profile for any IPv4 or IPv6 address you supply. Read risk level, environment score and AI service availability, plus a link to the full report on the provider's site. Results describe the network environment only, not account or subscription status.
When to use it
Useful when you suspect a proxy, VPN or datacenter IP is blocking access to AI services, or when comparing exit IPs before routing AI traffic through them.
Requirements
Runs locally via npx, so Node.js 20.18.1 or later is needed. No API key. Network access to the provider's site. To check the exit IP your AI traffic actually uses, the request must go through the same proxy; the server honors HTTPS_PROXY, HTTP_PROXY and NO_PROXY, which can be set in the client configuration.
Before you install
The server contacts the provider's site and sends it the IP being checked, so the provider sees your exit IP and any address you look up. It reads proxy environment variables from the environment. Results are network-environment signals only and should not be treated as proof that an account or subscription will work.

Installation

In SourceWeft

  1. Open IP for AI in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

ipforai-mcp

[npm]

MCP server for IP for AI: ask your AI assistant whether your current exit IP works for ChatGPT, Claude, Gemini and other AI services.

为 IP for AI 提供的 MCP 服务:在 Claude、Cursor 等 AI 客户端里直接检测当前出口 IP 能否正常使用 ChatGPT、Claude、Gemini 等 AI 服务。

Tools

ToolInputReturns
check_my_ipnoneProfile of this machine's IPv4 / IPv6 exit
lookup_ipip (IPv4 or IPv6)Profile of the given address

Each profile includes location, ASN, network type (residential / ISP / datacenter / proxy / Tor), access and routing type, risk level, an environment score, AI service availability, and a link to the full report on ipforai.cc.

Results describe the network environment only. They are not account, login or subscription verdicts.

Setup

Requires Node.js 20.18.1 or later. No API key.

Claude Code

bash
claude mcp add ipforai -- npx -y ipforai-mcp

Claude Desktop / Cursor / other clients

json
{  "mcpServers": {    "ipforai": {      "command": "npx",      "args": ["-y", "ipforai-mcp"]    }  }}

Proxy

check_my_ip reports the exit that ipforai.cc sees, so the request has to go through the same proxy your AI traffic uses. The server honors HTTPS_PROXY, HTTP_PROXY and NO_PROXY. TUN / transparent proxy modes need no setup. If your proxy is only set as the system proxy, pass it explicitly:

json
{  "mcpServers": {    "ipforai": {      "command": "npx",      "args": ["-y", "ipforai-mcp"],      "env": { "HTTPS_PROXY": "http://127.0.0.1:7890" }    }  }}

Privacy

The server only calls ipforai.cc (/json and the exit echo endpoints). It reads nothing from your machine besides the proxy environment variables.

License

MIT

Source: mcp/README.md at commit 69111a1

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestOct 14, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts