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

ferntool

https://www.ferntool.com

Registry code: 55d01642eb65c9c0

api record

Network tools from ferntool.com: IP geolocation with VPN/Tor/datacenter flags, batch IP lookup, RDAP WHOIS, DNS, reverse DNS and subnet calculator.

endpoint
https://www.ferntool.com/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 ferntool live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is ferntool free to use?
Yes — the hub reached it with no key and no payment.
What tools does ferntool have?
8 tools: batch_lookup_ip, whois_lookup, reverse_dns, validate_ip, dns_lookup, subnet_calc, lookup_ip, get_my_ip.
Is ferntool 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 100%· all time 100%

latency
219ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
1 open 7 never probed 1 of 8 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.

  • get_my_ip open 1h ago

    Return the public IP address (and ISP, ASN, location, timezone) of the caller as seen by FernTool. Note: for remote agents this is the IP of the machine calling the MCP server.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • batch_lookup_ip unknown 1h ago

    Look up 1-100 IPv4/IPv6 addresses at once. Each result has version, scope, country, timezone, ASN, network owner and flags (is_tor, is_datacenter, provider).

    mcp-tool

    {
  "type": "object",
  "required": [
    "ips"
  ],
  "properties": {
    "ips": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 100,
      "minItems": 1
    }
  }
}
    arguments 16 lines
  • whois_lookup unknown never probed

    WHOIS via RDAP for a domain (registrar, created/expiry dates, status, nameservers, DNSSEC), an IP address (network name, range, owner org, country, abuse contact) or an ASN like AS13335.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Domain, IPv4/IPv6 address, or ASN (e.g. AS13335)"
    }
  }
}
    arguments 12 lines
  • reverse_dns unknown never probed

    Reverse DNS (PTR) lookup for an IPv4/IPv6 address, with forward-confirmation check.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ip"
  ],
  "properties": {
    "ip": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • validate_ip unknown never probed

    Check whether a string is a valid IPv4 or IPv6 address and classify it.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ip"
  ],
  "properties": {
    "ip": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • dns_lookup unknown 1h ago

    Resolve DNS records for a domain via Cloudflare 1.1.1.1 DNS-over-HTTPS. Types: A, AAAA, MX, TXT, NS, CNAME, SOA (default: all).

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "types": {
      "type": "array",
      "items": {
        "enum": [
          "A",
          "AAAA",
          "MX",
          "TXT",
          "NS",
          "CNAME",
          "SOA"
        ],
        "type": "string"
      }
    },
    "domain": {
      "type": "string"
    }
  }
}
    arguments 26 lines
  • subnet_calc unknown never probed

    IPv4/IPv6 CIDR subnet calculator: network, netmask, wildcard, broadcast, first/last usable host, total and usable addresses, block type.

    mcp-tool

    {
  "type": "object",
  "required": [
    "cidr"
  ],
  "properties": {
    "cidr": {
      "type": "string",
      "description": "e.g. 192.168.1.0/24 or 2001:db8::/48"
    }
  }
}
    arguments 12 lines
  • lookup_ip unknown never probed

    Validate an IPv4/IPv6 address and return its version, scope (public/private/loopback/...), country, ASN and network owner (DB-IP Lite + IPtoASN data).

    mcp-tool

    {
  "type": "object",
  "required": [
    "ip"
  ],
  "properties": {
    "ip": {
      "type": "string",
      "description": "IPv4 or IPv6 address"
    }
  }
}
    arguments 12 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 55d01642eb65c9c0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/55d01642eb65c9c0/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/55d01642eb65c9c0/badge.svg)](https://brick.blue/agent/55d01642eb65c9c0?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
1
ok
1
failed
0
success rate
100%
median latency
284ms
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
—

1 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.