Skip to content
isipsafe logo

isipsafe MCP server

Which MCP servers are isipsafe's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-11-03

← Back to isipsafe

Whose server it is
  • Registry namecom.isipsafe/isipsafeverified in the MCP registry

The registry name sits under isipsafe.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-11-03
  • Stateanswerschecked 2026-11-03
  • Tools10
  • Server calls itselfisipsafe
  • Server version1.0
  • Protocol version2025-06-18

On 2026-11-03 the server answered initialize and tools/list without a sign-in. First answer in 326 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: check whether an IP address has attacked servers; report SSH brute-force sources from fail2ban; download a blocklist for firewall rules.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • For "check whether an IP address has attacked servers", the likely first call is check_ip.
  • For "report SSH brute-force sources from fail2ban", the likely first call is list_categories.
  • For "download a blocklist for firewall rules", the likely first call is get_blocklist.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-11-03
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • What an agent can do with it3 of 3 use cases
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer901 ms
  • Space in an agent's context≈ 1,649 tokensthe definitions of all its tools (10), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 10 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · check whether an IP address has attacked servers
  • can do · report SSH brute-force sources from fail2ban
  • can do · download a blocklist for firewall rules

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers10 tools · read 2026-11-03
  • check_ip

    Reputation of one IPv4 or IPv6 address: abuse confidence score (0-100, 75+ is on the blocklist), number of reports and distinct reporters, attack categories, country, network owner (ASN), Tor exit status and a link to its page. Set…

  • get_reports

    The individual abuse reports filed against one address, newest first, with time, categories, comment (usually log lines) and reporter. Paginated.

  • check_network

    Every reported address inside a CIDR block (IPv4 up to /16, IPv6 up to /48), with score, report count and last report time, plus the network's owner. Use it to judge a whole hosting range or subnet.

  • report_ip

    File an abuse report against an address that attacked a system you run. Needs an API key. Use category codes from list_categories (e.g. ssh,brute-force) and put the evidence (log lines, never personal data) in the comment. Each reporter…

  • get_blocklist

    The highest-confidence abusive addresses right now, best first, with score, country and categories. Needs an API key and counts as one blocklist download. For a firewall-ready file, point the firewall at the blocklist URL instead (see the…

  • list_categories

    All attack categories with their code, numeric ID, group and when to use them. Use the codes with report_ip.

  • get_statistics

    What the database sees right now: reports in the last 24 hours, addresses on the blocklist, and over the last 30 days the top attack categories, countries, networks and highest-scoring addresses.

  • get_country_report

    How many addresses in a country were reported in the last 30 days, how many are on the blocklist, the most reported addresses there, and the networks and attack categories behind them.

  • get_network_report

    Abuse reported against one autonomous system in the last 30 days: number of reported and blocklisted addresses, the worst addresses, attack categories and countries. Useful to judge a hosting provider or ISP.

  • about_isipsafe

    Explains isIPsafe itself. Use it for any question about the product rather than guessing: what it is and who it is for, its mission and aims, how reports and the confidence score work, plans, pricing and limits, how to get started, how to…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "isipsafe": {
      "type": "http",
      "url": "https://isipsafe.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http isipsafe https://isipsafe.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://isipsafe.com/mcp as a custom connector in the settings.

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.