Skip to content
IP 判官 logo

IP 判官

Looks up your public IP, ASN and WHOIS data so AI assistants and command-line tools can query it via API or MCP.
AgentsFor developers
ipjudge.org ↗
Open ipjudge.orgAlternativesSet it up for my teamIs IP 判官 yours? Claim the card →
At a glanceswept Oct 14, 2026

≈ 1visits/mo

Little sign of use · estimate, read Oct 14, 2026

Runs as
APICLI
Used for
  • look up whois and ASN records for an IP address
  • query IP details as JSON through an API or curl
  • check IPv4 and IPv6 connection information from a browser
Worth knowingcomputed from what we read · each with its source
How a program reaches itfound, not claimed · read Oct 21, 2026
  • MCP serverorg.ipjudge/ipjudgeverified in the MCP registry
  • Stateanswers, 4 toolschecked 2026-10-21
  • Address to connectipjudge.org/mcp
  • API docsipjudge.org/tools/apithe vendor's page ↗
  • MCP docsipjudge.org/tools/apithe vendor's page ↗

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Agentsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare IP 判官 with

Pick up to two.

All 10 alternatives to IP 判官 →

All Agents tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use IP 判官 for?

Sign in to leave a note
Questions this page answers
  • What is IP 判官?

    Looks up your public IP, ASN and WHOIS data so AI assistants and command-line tools can query it via API or MCP. It is listed in the Atlas under Agents.

  • Do people use IP 判官?

    Little sign of use: ≈ 1 visits/mo · estimate, 2026-10.

  • What are alternatives to IP 判官?

    In Agents, by use: uxspot MCP Server, AgentKey, Agents Base Phone Agents, Korely, SyntheticBrew, Emberverse.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk