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

isipsafe

https://isipsafe.com

Registry code: 8365810b21b927d1

api record

isipsafe is a community database of abusive IP addresses. Use check_ip before trusting or blocking an address, check_network for whole ranges, and get_country_report or get_network_report for the bigger picture. A score of 75 or more means the address is on the blocklist. Only use report_ip for abuse the user actually observed on systems they run. For questions about isipsafe itself (what it is, its mission, how scoring works, pricing, getting started, delisting, privacy, who runs it), call about_isipsafe and answer from what it returns. No API key was sent, so lookups use the anonymous…

endpoint
https://isipsafe.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 isipsafe live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is isipsafe free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does isipsafe have?
10 tools: list_categories, get_country_report, get_network_report, check_ip, get_reports, check_network, report_ip, get_statistics, ….
Is isipsafe 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
200ms

last good check

priced tools
0

of 10 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
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 10 tools
2 open1 auth-required 7 never probed 3 of 10 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_statistics open 2h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • about_isipsafe open 2h ago

    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 get an address delisted, privacy, and who runs it. Needs no API key and uses no allowance.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "topic": {
      "enum": [
        "overview",
        "mission",
        "how_it_works",
        "plans",
        "getting_started",
        "delisting",
        "privacy",
        "company",
        "faq"
      ],
      "type": "string",
      "default": "overview",
      "description": "What to read about. overview: What the product is, who it is for and what it offers. Start here. mission: Why it exists, what it aims for, its principles and where it is heading. how_it_works: How reports become a confidence score, what the score means, and where the data comes from. plans: What is free, the limits of each plan, Enterprise, and what the data may be used for. getting_started: How to look addresses up, report attacks, use the blocklist, the API, the integrations and MCP. delisting: What to do about an address that is listed, whether by mistake or for good reason. privacy: What is stored about reporters and visitors, public profiles, GDPR and deleting an account. company: The team, the company behind the service, contact details and legal documents. faq: Every question on the FAQ page: basics, reporting, scores, the blocklist and API, delisting and privacy."
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • get_blocklist auth-required 2h ago

    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 integrations).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 100,
      "maximum": 1000,
      "minimum": 1,
      "description": "Maximum number of addresses"
    },
    "ipVersion": {
      "enum": [
        4,
        6
      ],
      "type": "integer",
      "description": "Only IPv4 or only IPv6"
    },
    "onlyCountries": {
      "type": "string",
      "description": "Comma-separated ISO country codes to include, e.g. CN,RU"
    },
    "exceptCountries": {
      "type": "string",
      "description": "Comma-separated ISO country codes to leave out"
    },
    "confidenceMinimum": {
      "type": "integer",
      "default": 75,
      "maximum": 100,
      "minimum": 1,
      "description": "Lowest score to include"
    }
  },
  "additionalProperties": false
}
    arguments 36 lines
  • list_categories unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_country_report unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "country"
  ],
  "properties": {
    "country": {
      "type": "string",
      "description": "ISO 3166-1 alpha-2 code, e.g. DE"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_network_report unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "asn"
  ],
  "properties": {
    "asn": {
      "type": "string",
      "description": "AS number, with or without the AS prefix, e.g. AS14061 or 14061"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • check_ip unknown never probed

    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 verbose to include the latest reports with their comments.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ip"
  ],
  "properties": {
    "ip": {
      "type": "string",
      "description": "IPv4 or IPv6 address, e.g. 203.0.113.7"
    },
    "verbose": {
      "type": "boolean",
      "description": "Include up to 100 recent reports with comments"
    },
    "maxAgeInDays": {
      "type": "integer",
      "default": 30,
      "maximum": 365,
      "minimum": 1,
      "description": "Only count reports from the last N days"
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • get_reports unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "ip"
  ],
  "properties": {
    "ip": {
      "type": "string",
      "description": "IPv4 or IPv6 address"
    },
    "page": {
      "type": "integer",
      "default": 1,
      "maximum": 100000,
      "minimum": 1,
      "description": "Page number"
    },
    "perPage": {
      "type": "integer",
      "default": 25,
      "maximum": 100,
      "minimum": 1,
      "description": "Reports per page"
    },
    "maxAgeInDays": {
      "type": "integer",
      "default": 30,
      "maximum": 365,
      "minimum": 1,
      "description": "Only reports from the last N days"
    }
  },
  "additionalProperties": false
}
    arguments 34 lines
  • check_network unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "network"
  ],
  "properties": {
    "network": {
      "type": "string",
      "description": "CIDR block, e.g. 203.0.113.0/24"
    },
    "maxAgeInDays": {
      "type": "integer",
      "default": 30,
      "maximum": 365,
      "minimum": 1,
      "description": "Only count reports from the last N days"
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • report_ip unknown never probed

    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 can report the same address once per 15 minutes. Only report real, observed abuse.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ip",
    "categories"
  ],
  "properties": {
    "ip": {
      "type": "string",
      "description": "The attacking IPv4 or IPv6 address"
    },
    "comment": {
      "type": "string",
      "description": "Evidence: what happened, ideally the relevant log lines"
    },
    "timestamp": {
      "type": "string",
      "description": "When the attack happened, ISO 8601 (optional, defaults to now)"
    },
    "categories": {
      "type": "string",
      "description": "Comma-separated category codes or numeric IDs, e.g. ssh,brute-force"
    }
  },
  "additionalProperties": false
}
    arguments 26 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 8365810b21b927d1.

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