nodemaven-mcp
An MCP server for NodeMaven residential proxies. It lets an AI assistant build proxy strings with geo-targeting and sticky sessions, check that a proxy connects and where it exits, look up locations, and read traffic usage.
It is read-only: nothing in your account is created, changed or deleted.
Tools
| Tool | What it does |
|---|---|
proxy_url |
Proxy string for a country, region, city or ISP, with an optional sticky session and its lifetime. HTTP or SOCKS5. |
check_proxy |
Opens one connection through the proxy and returns the status, the exit IP and the time it took. |
list_locations |
Countries, regions, cities and ISPs available for targeting, with the codes proxy_url takes. |
account_status |
Remaining traffic, subscription status, whether traffic is frozen. |
traffic_stats |
Traffic used over time. |
top_domains |
Domains reached through the proxy, with traffic per domain. |
list_sub_users |
Sub-users with their usage and limits. |
Setup
You need an API key from the NodeMaven dashboard. The proxy username and password are read from the account through that key, so nothing else is required.
Claude Desktop (claude_desktop_config.json), Cursor and other MCP clients:
{
"mcpServers": {
"nodemaven": {
"command": "uvx",
"args": ["nodemaven-mcp"],
"env": { "NODEMAVEN_APIKEY": "your-api-key" }
}
}
}
Without uv: pip install nodemaven-mcp and use "command": "nodemaven-mcp".
| Variable | |
|---|---|
NODEMAVEN_APIKEY |
Required. |
NODEMAVEN_LOGIN, NODEMAVEN_PASSWORD |
Optional. Proxy credentials to use instead of the account's own, e.g. a sub-user. |
NODEMAVEN_MCP_REVEAL_PASSWORD |
1 puts the real password into proxy_url output. Off by default. |
Credentials
Tool results go into the model's context and usually into the chat history, so the server keeps secrets out of them:
proxy_urlreturns the password as<PROXY_PASSWORD>unlessNODEMAVEN_MCP_REVEAL_PASSWORD=1is set.- API responses are reduced to a fixed list of fields; proxy passwords and the account email are never returned.
Development
uv sync
uv run pytest
Built on the nodemaven Python SDK.
License
MIT
Metadata
Release files for nodemaven-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| nodemaven_mcp-0.1.0.tar.gz | 8.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nodemaven_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.7 kB
Release files / nodemaven_mcp-0.1.0.tar.gz
| Download URL | nodemaven_mcp-0.1.0.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cf59a02aca20146352990ac7172b643ebc962a36e2f34231ce29967bcdec2134
|
|
BLAKE2b-256 checksum How to use checksums |
809ab9a041eebeae4a9cbe21a75efbe7ef23b887d04db99e9bd4e5c0e7fc2f84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency logRelease files / nodemaven_mcp-0.1.0-py3-none-any.whl
| Download URL | nodemaven_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
13c6cad6158dbe549ee28e58682c096b6e809cf106798e21f23505e7a2944b35
|
|
BLAKE2b-256 checksum How to use checksums |
d3abd46273477144ca5758fe246f21995e963a1622ab7e330faaf9ff59e51a03
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency log