
Official MCP RegistryListed
isIPsafe
Check whether an IP address or network is malicious and report abusive IPs to isIPsafe.
First seen 3 Nov 2026. Evidence as of 16 Nov 2026.
12
Tools
From an anonymous probe
1
Source listings
Each with its own history
6
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| 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 get an address delisted, privacy, and who runs it. Needs no API key and uses no allowance. | Read-only |
| analyze_logs | Find malicious traffic in logs. Pass raw log lines from any source (nginx/Apache/IIS access logs, sshd/auth.log, syslog, firewall such as iptables/UFW/pfSense/ASA, mail servers, Windows events as text, CEF, JSON lines from a SIEM or cloud, CSV); every IPv4/IPv6 address is extracted wherever it appears and each non-blank line is one event. Returns how many events came from malicious (score 75+), suspicious (25-74) and unreported addresses, the top offenders with score and attack categories, the busiest addresses, countries, networks, attack categories, detected log formats, HTTP status classes, failed logins and the time range. Each distinct address looked up counts as one lookup against the daily allowance, busiest first. Per analysis: without a key 256 KB and 100 addresses, free key 2 MB and 1,000, Enterprise 5 MB and 10,000. The log is not stored. Remove secrets (passwords, tokens) before sending. | Read-only |
| 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 verbose to include the latest reports with their comments. | Read-only |
| 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. | Read-only |
| 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 integrations). | Read-only |
| 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. | Read-only |
| 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. | Read-only |
| get_reports | The individual abuse reports filed against one address, newest first, with time, categories, comment (usually log lines) and reporter. Paginated. | Read-only |
| 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. | Read-only |
| get_today_news | Today's threat news from the last 24 hours: the countries the most reported attacks come from, the networks (ASNs) behind them, the attack techniques (categories) reported most, and the top 10 malicious IP addresses reported today, highest score first. Use it for a daily briefing on what is attacking right now. | Read-only |
| list_categories | All attack categories with their code, numeric ID, group and when to use them. Use the codes with report_ip. | Read-only |
| 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 can report the same address once per 15 minutes. Only report real, observed abuse. | Changes data |
Change history
- get_today_news: tool added
- analyze_logs: tool added
- server instructions changed (+"analyze_logs to find malicious traffic in log lines the user shares,")
- Website changed from "https://isipsafe.com/mcp-server" to "https://isipsafe.com" (registry)
- Repository changed (registry)
- Listed (registry)
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Official MCP Registry | com.isipsafe/isipsafe | 3 Nov 2026 | 16 Nov 2026 | 2 |