NodeMaven
PYPI · NODEMAVEN-MCP
NodeMaven residential proxies: geo-targeted proxy URLs, sticky sessions, checks and usage
Available components
Last scanned (4 hours ago)
Scores higher than 65% of PyPI servers
Category Cloud Infrastructure
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 30 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 nodemaven/nodemaven-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 16 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 626 tokens (~89/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 23 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 22 Oct 26 +3
- Stability: unverified → 0.27 ▲ functional
- 14 Oct 26 +43
- Injection markers: unverified → pass ▲ security
- Malware scan: 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 Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 13 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 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 23 Oct 2026 · Analysed pypi/nodemaven-mcp@0.1.0
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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | nodemaven/nodemaven-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/nodemaven/nodemaven-mcp/.github/workflows/publish.yml@refs/tags/v0.1.0 |
| Rekor log index | 3110561682 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:cf59a02aca20146352990ac7172b643ebc962a36e2f34231ce29967bcdec2134 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 30 packages
| Packages resolved | 30 |
|---|---|
| No linked repository | 1 |
| 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 →
account_status ~21
Remaining traffic (bytes), subscription status and whether traffic is frozen.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
check_proxy ~101
Open one connection through the proxy and report the result. Sends no traffic through the tunnel. Returns the gateway status, the exit IP when the gateway reports it, and how long the connection took. A 407 can mean a wrong parameter value as well as wrong credentials.
| Name | Type | Req | Description |
|---|---|---|---|
| city | – | – | – |
| country | – | – | – |
| filter | – | – | – |
| isp | – | – | – |
| region | – | – | – |
| session_id | – | – | – |
| ttl | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_locations ~107
List locations available for targeting, with the codes proxy_url takes. regions need country_code; cities and isps can be narrowed by country_code and region_code. At most 100 rows per call: when next_offset is returned, call again with offset=next_offset for the rest.
| Name | Type | Req | Description |
|---|---|---|---|
| connection_type | string | – | – |
| country_code | – | – | – |
| kind | string | yes | – |
| limit | integer | – | – |
| offset | integer | – | – |
| region_code | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_sub_users ~61
Sub-users of the account with their traffic usage and limits. No passwords. Paged from page 1. When next_page is returned, call again with it for the rest; a page past the end comes back empty.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
proxy_url ~149
Build a NodeMaven proxy string. Targeting goes into the username. Without session_id every request gets a new exit IP; with session_id the same exit is kept for ttl (e.g. "10m", "1h", "24h"). country is a two-letter code; region, city and isp take the codes from list_locations. filter is the IP quality filter, e.g. "medium". The password is a placeholder unless the server allows revealing it.
| Name | Type | Req | Description |
|---|---|---|---|
| city | – | – | – |
| country | – | – | – |
| filter | – | – | – |
| isp | – | – | – |
| protocol | string | – | – |
| region | – | – | – |
| session_id | – | – | – |
| ttl | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
top_domains ~65
Domains reached through the proxy, largest traffic first, with bytes and request counts. Pass period, or start and end as dd-mm-yyyy (not ISO). Defaults to today.
| Name | Type | Req | Description |
|---|---|---|---|
| end | – | – | – |
| limit | integer | – | – |
| period | – | – | – |
| start | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
traffic_stats ~54
Traffic used over time, as parallel labels and data arrays. Pass period, or start and end as dd-mm-yyyy (not ISO). Defaults to today.
| Name | Type | Req | Description |
|---|---|---|---|
| end | – | – | – |
| period | – | – | – |
| start | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the NodeMaven MCP server?
NodeMaven runs locally as a PyPI package, launched with uvx nodemaven-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · nodemaven-mcp
claude mcp add nodemaven-nodemaven-mcp -- uvx nodemaven-mcp
What is the NodeMaven MCP server?
NodeMaven is an MCP server listed in the public MCP registry as io.github.nodemaven/nodemaven-mcp. NodeMaven residential proxies: geo-targeted proxy URLs, sticky sessions, checks and usage. This page covers its PyPI package (nodemaven-mcp).
Is the NodeMaven MCP server safe to use?
NodeMaven scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. 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 NodeMaven MCP server expose?
NodeMaven exposes 7 tools: proxy_url, check_proxy, list_locations, account_status, traffic_stats, and 2 more. Their descriptions and schemas cost roughly 558 tokens of context every time the server is loaded.
Is the NodeMaven MCP server still maintained?
NodeMaven is still listed as active in the MCP registry. We last reached this channel on 23 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 NodeMaven MCP server under?
NodeMaven declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.