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

IP Lookup Service (ipls)

https://ip.ls

Registry code: f59b679b79d38561

api record

Keyless IP geolocation, ASN/ISP, timezone and DNS records for any IP or domain, plus your own IP.

from a public catalogue that lists it, not from the operator

endpoint
https://ip.ls/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 IP Lookup Service (ipls) live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is IP Lookup Service (ipls) free to use?
Yes — the hub reached it with no key and no payment.
What tools does IP Lookup Service (ipls) have?
6 tools: ip_lookup, ip_resolved, ip_summary, ip_self, ua, headers.
Is IP Lookup Service (ipls) 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
100%

90 days 99.7%· all time 99.7%

latency
579ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 679 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • geolocate an ip address
  • resolve a domain's ip addresses
  • get my own public ip
  • summarize a batch of ips
takes → gives
text → data
tools
6 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 6 tools
3 open 3 never probed 3 of 6 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.

  • ip_self reads open 11h ago

    Get geolocation and network info about the caller's own public IP, plus the protocol stack (IPv4/IPv6) of the current connection. On dual-stack machines the stack is chosen by the client and may differ from `curl ip.ls`, which picks a random stack; use curl -4/-6 locally to get the other stack, or — for clients that cannot pick a stack (browser, PowerShell, most HTTP libraries) — the single-stack hostnames https://4.ip.ls / https://6.ip.ls (DNS selects the stack; an unreachable 6.ip.ls means no usable IPv6). Data comes from a server-side GeoIP lookup on the caller's real IP.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • ua reads open 11h ago

    Return the User-Agent string of the current HTTP client.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • headers reads open 11h ago

    Return all HTTP request headers as seen by the IP.LS server (including X-Real-IP / X-Forwarded-For injected by the frontend proxy). Useful for debugging proxies and client identity.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • ip_lookup reads unknown 6h ago

    Look up geolocation, ISP and network info for any IPv4/IPv6 address or hostname, or an array of them for batch lookup. Returns ip, city, region, country, coordinates, ASN/ISP, timezone and continent (full name, e.g. North America); when a domain is queried, an extra `domain` field echoes it. Data source: DB-IP Lite (CC BY 4.0). Anycast IPs are approximate.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ip"
      ],
      "properties": {
        "ip": {
          "type": [
            "string",
            "array"
          ],
          "items": {
            "type": "string"
          },
          "description": "IPv4/IPv6 address or hostname, e.g. 8.8.8.8 or example.com. Pass an array for batch lookup, e.g. [\"8.8.8.8\", \"1.1.1.1\"]."
        }
      }
    }
    arguments 18 lines
  • ip_resolved reads unknown 6h ago

    Resolve a domain to all its A and AAAA records (deduplicated, up to 6) and return geolocation for each address. Returns an array of { ip, protocol, domain, city, region, country, coordinates, ASN/ISP, ... }. For a bare IP, returns a single-element array.

    mcp-tool

    {
      "type": "object",
      "required": [
        "host"
      ],
      "properties": {
        "host": {
          "type": "string",
          "description": "Domain or IP address to resolve, e.g. example.com or baidu.com"
        }
      }
    }
    arguments 12 lines
  • ip_summary reads unknown 6h ago

    Summarize a large batch of IPs into distributions by country, continent, ASN/operator and network prefix, each bucket with a sample of addresses. Use instead of ip_lookup once the input is in the hundreds or thousands — ip_lookup returns every row, which no context window holds. Up to 5000 addresses or 100 hostnames. Counts are per occurrence; nothing is dropped silently (failed → `errors`, no database record → `no_data`, unlisted buckets → `tail`), the same input set always returns the same numbers, and the result is facts only — no datacenter/residential classification, no verdict. DB-IP Lite (CC BY 4.0).

    mcp-tool

    {
      "type": "object",
      "required": [
        "ips"
      ],
      "properties": {
        "ips": {
          "anyOf": [
            {
              "type": "string",
              "description": "Whitespace- or comma-separated (paste a log column)."
            },
            {
              "type": "array",
              "items": {
                "type": "string"
              },
              "maxItems": 5000,
              "description": "e.g. [\"8.8.8.8\",\"example.com\"]."
            }
          ]
        },
        "top": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1,
          "description": "Buckets per dimension."
        },
        "sample": {
          "type": "integer",
          "default": 3,
          "maximum": 5,
          "minimum": 0,
          "description": "Sample addresses per bucket."
        },
        "prefix4": {
          "type": "integer",
          "default": 24,
          "maximum": 32,
          "minimum": 8,
          "description": "IPv4 grouping prefix."
        },
        "prefix6": {
          "type": "integer",
          "default": 48,
          "maximum": 64,
          "minimum": 16,
          "description": "IPv6 grouping prefix; /48 = one end-site."
        }
      },
      "additionalProperties": false
    }
    arguments 53 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 f59b679b79d38561.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f59b679b79d38561/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/f59b679b79d38561/badge.svg)](https://brick.blue/agent/f59b679b79d38561?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
100%

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.