Koskamo

isIPsafe MCP

An official MCP server for isIPsafe that allows agents to check IP addresses and networks for malicious activity, report abusive IPs, download blocklists, analyze logs for malicious traffic, and retrieve statistics and news about top attacking countries and networks.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

isIPsafe MCP logo, by isIPsafeVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by isIPsafe
You need:Send the API key as "Authorization: Bearer YOUR_KEY" or ?key=.
MCP endpoint (Streamable HTTP)
https://isipsafe.com/mcp
Vendor documentation

What its tools do

12 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Read-only (11)

Can change data (1)

12 of 12 have a description · 12 of 12 declare behavior hints · 9 of 9 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to isipsafe.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Check if an IP address is malicious
  • Report abusive IP addresses
  • Analyze logs for malicious traffic
  • Download IP blocklists

Source and maintenance

Vendor evidenceRegistry 1.0.1
mcp-registry: com.isipsafe/isipsafe@1.0.1Source repositoryProject website
Maintenance checked

Protocol and capabilities

Server
isipsafe 1.0
MCP protocol negotiated in check
2025-11-25
Tools
12 advertised
Resources
9 advertised
Resource templates
0 advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  },
  "resources": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

isipsafe is a community database of abusive IP addresses. Use check_ip before trusting or blocking an address, check_network for whole ranges, analyze_logs to find malicious traffic in log lines the user shares, 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 allowance and report_ip and get_blocklist are unavailable.

Tools

12 advertised

check_ip — Check an IP address
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

check_ip input schema
{
  "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
}
check_ip annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
get_reports — List reports for an IP address
Advertised by the server during the last successful anonymous check.
Advertised read-only

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

get_reports input schema
{
  "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
}
get_reports annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
check_network — Check a network (CIDR)
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

check_network input schema
{
  "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
}
check_network annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
report_ip — Report an abusive IP address
Advertised by the server during the last successful anonymous check.
Open-world

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.

report_ip input schema
{
  "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
}
report_ip annotations
{
  "readOnlyHint": false,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}
get_blocklist — Get the blocklist
Advertised by the server during the last successful anonymous check.
Advertised read-only

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

get_blocklist input schema
{
  "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
}
get_blocklist annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
list_categories — List report categories
Advertised by the server during the last successful anonymous check.
Advertised read-only

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

list_categories input schema
{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
list_categories annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
get_statistics — Current abuse statistics
Advertised by the server during the last successful anonymous check.
Advertised read-only

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_statistics input schema
{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
get_statistics annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
get_today_news — Today News
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

get_today_news input schema
{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
get_today_news annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
analyze_logs — Analyze log traffic
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

analyze_logs input schema
{
  "type": "object",
  "required": [
    "logs"
  ],
  "properties": {
    "logs": {
      "type": "string",
      "description": "The raw log text, one event per line, in any format"
    }
  },
  "additionalProperties": false
}
analyze_logs annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
get_country_report — Abuse report for a country
Advertised by the server during the last successful anonymous check.
Advertised read-only

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_country_report input schema
{
  "type": "object",
  "required": [
    "country"
  ],
  "properties": {
    "country": {
      "type": "string",
      "description": "ISO 3166-1 alpha-2 code, e.g. DE"
    }
  },
  "additionalProperties": false
}
get_country_report annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
get_network_report — Abuse report for a network (ASN)
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

get_network_report input schema
{
  "type": "object",
  "required": [
    "asn"
  ],
  "properties": {
    "asn": {
      "type": "string",
      "description": "AS number, with or without the AS prefix, e.g. AS14061 or 14061"
    }
  },
  "additionalProperties": false
}
get_network_report annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
about_isipsafe — About isIPsafe
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

about_isipsafe input schema
{
  "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
}
about_isipsafe annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

9 advertised

overview — What isipsafe is

Advertised by the server during the last successful anonymous check.

What the product is, who it is for and what it offers. Start here.

overview URI
isipsafe://about/overview

MIME type: text/markdown

mission — The mission of isipsafe

Advertised by the server during the last successful anonymous check.

Why it exists, what it aims for, its principles and where it is heading.

mission URI
isipsafe://about/mission

MIME type: text/markdown

how_it_works — How isipsafe works

Advertised by the server during the last successful anonymous check.

How reports become a confidence score, what the score means, and where the data comes from.

how_it_works URI
isipsafe://about/how_it_works

MIME type: text/markdown

plans — Plans, pricing and limits

Advertised by the server during the last successful anonymous check.

What is free, the limits of each plan, Enterprise, and what the data may be used for.

plans URI
isipsafe://about/plans

MIME type: text/markdown

getting_started — Getting started with isipsafe

Advertised by the server during the last successful anonymous check.

How to look addresses up, report attacks, use the blocklist, the API, the integrations and MCP.

getting_started URI
isipsafe://about/getting_started

MIME type: text/markdown

delisting — Getting an address removed

Advertised by the server during the last successful anonymous check.

What to do about an address that is listed, whether by mistake or for good reason.

delisting URI
isipsafe://about/delisting

MIME type: text/markdown

privacy — Privacy and data

Advertised by the server during the last successful anonymous check.

What is stored about reporters and visitors, public profiles, GDPR and deleting an account.

privacy URI
isipsafe://about/privacy

MIME type: text/markdown

company — Who runs isipsafe and how to reach them

Advertised by the server during the last successful anonymous check.

The team, the company behind the service, contact details and legal documents.

company URI
isipsafe://about/company

MIME type: text/markdown

faq — Frequently asked questions

Advertised by the server during the last successful anonymous check.

Every question on the FAQ page: basics, reporting, scores, the blocklist and API, delisting and privacy.

faq URI
isipsafe://about/faq

MIME type: text/markdown

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1825 ms
95th percentile latency
1825 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1825 ms · metadata changed · 12 tool(s), 9 resource(s), 0 resource template(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http isipsafe-mcp https://isipsafe.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add isipsafe-mcp --url https://isipsafe.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable isipsafe-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "isipsafe-mcp": {
      "url": "https://isipsafe.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "isipsafe-mcp": {
      "type": "streamableHttp",
      "url": "https://isipsafe.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start isipsafe-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "isipsafe-mcp": {
      "type": "http",
      "url": "https://isipsafe.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http isipsafe-mcp https://isipsafe.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://isipsafe.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "isipsafe-mcp": {
      "serverUrl": "https://isipsafe.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like isIPsafe MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 5,158

Do you run isIPsafe MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing