isIPsafe
v1.0.1Check whether an IP address or network is malicious and report abusive IPs to isIPsafe.
Endpoint health
online- Last checked
- 11/20/2026, 3:17:56 AM
- Latency
- 147 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.isipsafe%2Fisipsafe
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.isipsafe/isipsafe": {
"url": "https://isipsafe.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
12 shown · authentication unknown
About isIPsafe
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.
Schema valid · SHA-256 ac94176932ce…
View input schema
{ "type": "object", "properties": { "topic": { "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.", "enum": [ "overview", "mission", "how_it_works", "plans", "getting_started", "delisting", "privacy", "company", "faq" ], "type": "string" } }, "additionalProperties": false }Analyze log traffic
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.
Connections
streamable-http
https://isipsafe.com/mcp