FindIP
NPM · @FINDIP/MCP
IP intelligence lookups and FindIP Shield visitor risk signals for AI assistants.
Available components
Last scanned (12 hours ago)
Scores higher than 82% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to findip-net/findip-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 554 tokens (~110/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
- 14 Oct 26 +32
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 13 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 12 Oct 26 49
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Oct 2026 · Analysed npm/@findip/mcp@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | findip-net/findip-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/findip-net/findip-mcp/.github/workflows/publish.yml@refs/tags/v0.1.1 |
| Rekor log index | 3206715580 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:0b14322a1733ce9857906c69ed21d731c863981297cc7ca9bc1e5b9f719931fef13b214940a809cbbc563106d722035615d937ce73f94f76c836c1f8b |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
explain_event Explain a Shield event ~92
Explains one Shield event in plain language: where it came from, which risk signals fired, the score and recommendation, and what the in-page SDK did. The explanation describes risk signals, not a verdict about the visitor.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | Event ID from recent_risky_events |
| site | string | – | Site ID, name or domain. Optional; without it each of your sites is checked |
No output schema declared.
No examples provided.
list_shield_sites List Shield sites ~49
Lists the FindIP Shield sites on your account: ID, name, domain, status, last event time and today's event and risky-event counts. Start here to find the site to ask about.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_ip Look up an IP address ~94
IP intelligence for one IPv4 or IPv6 address from FindIP: country, city, ISP and ASN, connection type, and risk signals (VPN, proxy, Tor, relay, hosting, scanner, malicious listings, threat score). Signals describe the network an address belongs to, not the person using it.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | IPv4 or IPv6 address, for example 8.8.8.8 |
No output schema declared.
No examples provided.
recent_risky_events Recent risky events ~163
Recent events on one Shield site at or above a risk score, newest first: event name, page, IP, country, network, network signals, score, recommendation and reasons. Good for questions like "what risky traffic hit my signup form this week". End-user identity is never returned.
| Name | Type | Req | Description |
|---|---|---|---|
| event_name | string | – | Only this event, for example signup_attempt, login_attempt or payment_attempt |
| limit | integer | – | Maximum events to return. Default 25 |
| min_risk_score | integer | – | Lowest risk score to include. Default 50 (high and critical) |
| range | string | – | Time window. Default 7d |
| site | string | yes | Site ID, name or domain, as shown by list_shield_sites |
No output schema declared.
No examples provided.
verify_session Verify a Shield session ~156
Server-side risk check for one FindIP Shield session: risk score, recommendation (allow, monitor, challenge, block), whether a challenge was passed, and the session picture (IP, ASN and country rotation, network flags, risk reasons). This is the same check a backend runs before acting on a signup, login or checkout. An unknown session returns verified: false; a session without IP intelligence returns risk_status "unknown", which is not the same as safe. Uses the site secret key from FINDIP_SHIELD_SECRET_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | – | Optional event the check is for, for example signup_attempt |
| session_id | string | yes | Shield session ID sent by the browser SDK (FindIP.getSession().sessionId) |
No output schema declared.
No examples provided.
How do I install the FindIP MCP server?
FindIP runs locally as an npm package, launched with npx -y @findip/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @findip/mcp
claude mcp add findip-net-findip-mcp -- npx -y @findip/mcp
What is the FindIP MCP server?
FindIP is an MCP server listed in the public MCP registry as io.github.findip-net/findip-mcp. IP intelligence lookups and FindIP Shield visitor risk signals for AI assistants. This page covers its npm package (@findip/mcp).
Is the FindIP MCP server safe to use?
FindIP scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the FindIP MCP server expose?
FindIP exposes 5 tools: lookup_ip, verify_session, list_shield_sites, recent_risky_events, explain_event. Their descriptions and schemas cost roughly 554 tokens of context every time the server is loaded.
Is the FindIP MCP server still maintained?
FindIP is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the FindIP MCP server under?
FindIP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.