_ registry / mcp streamable-http · checked 2h ago

ipjudge

https://ipjudge.org

Registry code: 41a250f63bd93ee1

api record

Neutral IP / network-exit checks for AI accounts (ChatGPT, Claude, Gemini, Muse). Use my_exit to check the machine you run on.

endpoint
https://ipjudge.org/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is ipjudge live?
Yes — it answered the hub's last check (checked 2h ago). It answered 97% of checks over the last 30 days.
Is ipjudge free to use?
Yes — the hub reached it with no key and no payment.
What tools does ipjudge have?
4 tools: my_exit, ai_availability, check_ip, service_status.
Is ipjudge safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
97%

90 days 97.8%· all time 97.8%

latency
713ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 369 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • check whether an ip is residential or datacenter
  • check own network exit ip
  • check which countries ai services support
  • get live status of ai and cloud services
takes → gives
text → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • service_status reads open 21h ago

    Official live status (Statuspage) of Claude, OpenAI, Cursor, GitHub, Cloudflare and more, refreshed every 3 minutes.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "service": {
          "type": "string",
          "description": "optional key, e.g. claude, openai"
        }
      }
    }
    arguments 9 lines
  • my_exit reads unknown never probed

    Judge the public IP this agent/server is calling from (its own network exit) — use it to check whether Claude / ChatGPT will accept the machine the agent runs on.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "lang": {
          "enum": [
            "en",
            "zh"
          ],
          "type": "string",
          "default": "en"
        }
      }
    }
    arguments 13 lines
  • ai_availability reads unknown never probed

    Whether ChatGPT, Claude, Gemini and Muse officially support a country (ISO 3166-1 alpha-2, e.g. US, HK, CN), from each company's published list.

    mcp-tool

    {
      "type": "object",
      "required": [
        "country"
      ],
      "properties": {
        "country": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • check_ip reads unknown 21h ago

    Judge an IPv4/IPv6 address: residential vs datacenter, purity score 0-100, risk-list hits, and whether ChatGPT, Claude, Gemini and Muse accept its region/type. Data: ipjudge.org.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ip"
      ],
      "properties": {
        "ip": {
          "type": "string",
          "description": "IPv4 or IPv6 address"
        },
        "lang": {
          "enum": [
            "en",
            "zh"
          ],
          "type": "string",
          "default": "en"
        }
      }
    }
    arguments 20 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 41a250f63bd93ee1.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/41a250f63bd93ee1/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/41a250f63bd93ee1/badge.svg)](https://brick.blue/agent/41a250f63bd93ee1?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.