Local MCP capabilities provider for Expo
Nothing to run from here
isIPsafe is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
10
tools declared
remote
at its publisher
—
calls last 7d
What it does
Check whether an IP address or network is malicious and report abusive IPs to isIPsafe.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http isipsafe-mcp https://isipsafe.com/mcp
# 2 — ask your agent for something these tools do
# check_ip, get_reports, check_network and 7 more
isIPsafe costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ISAll 1 server
isipsafe1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http isipsafe-mcp https://isipsafe.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take X-API-Key header (isIPsafe API key. Optional for lookups, needed to report IPs. Get one at https://isipsafe.com/account) if you want to set it.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ip | string | yes | IPv4 or IPv6 address, e.g. 203.0.113.7 |
| maxAgeInDays | integer | no | Only count reports from the last N days |
| verbose | boolean | no | Include up to 100 recent reports with comments |
The individual abuse reports filed against one address, newest first, with time, categories, comment (usually log lines) and reporter. Paginated.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ip | string | yes | IPv4 or IPv6 address |
| maxAgeInDays | integer | no | Only reports from the last N days |
| page | integer | no | Page number |
| perPage | integer | no | Reports per page |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| maxAgeInDays | integer | no | Only count reports from the last N days |
| network | string | yes | CIDR block, e.g. 203.0.113.0/24 |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| categories | string | yes | Comma-separated category codes or numeric IDs, e.g. ssh,brute-force |
| comment | string | no | Evidence: what happened, ideally the relevant log lines |
| ip | string | yes | The attacking IPv4 or IPv6 address |
| timestamp | string | no | When the attack happened, ISO 8601 (optional, defaults to now) |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| confidenceMinimum | integer | no | Lowest score to include |
| exceptCountries | string | no | Comma-separated ISO country codes to leave out |
| ipVersion | integer | no | Only IPv4 or only IPv6 |
| limit | integer | no | Maximum number of addresses |
| onlyCountries | string | no | Comma-separated ISO country codes to include, e.g. CN,RU |
All attack categories with their code, numeric ID, group and when to use them. Use the codes with report_ip.
No parameter schema on file.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 code, e.g. DE |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asn | string | yes | AS number, with or without the AS prefix, e.g. AS14061 or 14061 |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | 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 rep |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install isIPsafe or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.1 · scanned 4 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest73de2c90b8dc02826edb0776af5293f858bfcad15bdddff279049fde24742f21
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| check_ip | no tags | |
| get_reports | no tags | |
| check_network | no tags | |
| report_ip | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| get_blocklist | untrusted-input | untrusted-input: keyword "download" |
| list_categories | no tags | |
| get_statistics | no tags | |
| get_country_report | no tags | |
| get_network_report | no tags | |
| about_isipsafe | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest73de2c90b8dc0282
Scanned2026-11-04
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
1.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish isIPsafe can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.