Ipqualityscore
NPM · @PIPEWORX/MCP-IPQUALITYSCORE · 2 COMPONENTS
IPQualityScore MCP — wraps the IPQualityScore fraud-prevention API (ipqualityscore.com).
Available components
Last scanned (30 minutes ago)
Scores higher than 76% 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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-ipqualityscore). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 738 tokens (~184/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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 4 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-ipqualityscore@0.2.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 | pipeworx-io/mcp-ipqualityscore |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-ipqualityscore/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637485563 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4cace3818cd0aab5292255d88157fad8854e9f0a75a68992a6f398a15da5294a7e7b793c93baa2c00ac0a563174d4cebf3a7bfc6c9b2101ff0e08c1cd |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
check_email ~144
Email fraud & deliverability check. Validates an email address, detects disposable/temporary addresses, flags emails seen in data leaks, and returns a 0-100 fraud score plus deliverability, SMTP, and DNS validity signals. Example: check_email({ email: "user@example.com" }) Requires your own IPQualityScore API key, passed as _apiKey.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your own IPQualityScore API key (BYO — Pipeworx does not supply one). Free tier at ipqualityscore.com; the key is on the account dashboard. |
| string | yes | Email address to validate, e.g. "user@example.com" |
No output schema declared.
No examples provided.
check_ip ~210
Fraud detection & risk scoring for an IP address. Answers "is this IP a proxy, VPN, or Tor exit node?", flags bots/crawlers and recent abuse, and returns a 0-100 fraud score plus geolocation (country, region, city, ISP, connection type). Example: check_ip({ ip: "8.8.8.8", strictness: 1 }) Requires your own IPQualityScore API key, passed as _apiKey.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your own IPQualityScore API key (BYO — Pipeworx does not supply one). Free tier at ipqualityscore.com; the key is on the account dashboard. |
| ip | string | yes | IPv4 or IPv6 address to check, e.g. "8.8.8.8" |
| strictness | number | – | Detection strictness 0, 1, or 2. Higher = more aggressive proxy/VPN detection (more false positives). Default 1. |
No output schema declared.
No examples provided.
check_phone ~187
Phone number validation & fraud check. Confirms whether a number is valid and active, returns a 0-100 fraud score, and flags VOIP, prepaid, and risky numbers with line type, carrier, and region. Example: check_phone({ phone: "18007267864", country: "US" }) Requires your own IPQualityScore API key, passed as _apiKey.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your own IPQualityScore API key (BYO — Pipeworx does not supply one). Free tier at ipqualityscore.com; the key is on the account dashboard. |
| country | string | – | Optional 2-letter ISO country code to improve parsing, e.g. "US", "GB". |
| phone | string | yes | Phone number to validate, e.g. "18007267864" or "+1 800 726 7864" |
No output schema declared.
No examples provided.
check_url ~143
URL / malware safety scan. Checks whether a URL or domain is unsafe — phishing, malware, spam — and returns a risk score, domain reputation rank, content category, DNS validity, and domain age. Example: check_url({ url: "https://example.com" }) Requires your own IPQualityScore API key, passed as _apiKey.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your own IPQualityScore API key (BYO — Pipeworx does not supply one). Free tier at ipqualityscore.com; the key is on the account dashboard. |
| url | string | yes | Full URL or domain to scan, e.g. "https://example.com" |
No output schema declared.
No examples provided.
How do I install the Ipqualityscore MCP server?
Ipqualityscore runs locally as an npm package, launched with npx -y @pipeworx/mcp-ipqualityscore. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-ipqualityscore
claude mcp add pipeworx-io-ipqualityscore -- npx -y @pipeworx/mcp-ipqualityscore
What is the Ipqualityscore MCP server?
Ipqualityscore is an MCP server listed in the public MCP registry as io.github.pipeworx-io/ipqualityscore. IPQualityScore MCP, wraps the IPQualityScore fraud-prevention API (ipqualityscore.com). This page covers its npm package (@pipeworx/mcp-ipqualityscore).
Is the Ipqualityscore MCP server safe to use?
Ipqualityscore scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 Ipqualityscore MCP server expose?
Ipqualityscore exposes 4 tools: check_ip, check_email, check_phone, check_url. Their descriptions and schemas cost roughly 684 tokens of context every time the server is loaded.
Is the Ipqualityscore MCP server still maintained?
Ipqualityscore is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Ipqualityscore MCP server under?
Ipqualityscore declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.