Back to Browse

Nodemaven MCP Server

Developer ToolsLow Risk10.0MCP RegistryLocal
Free

Server data from the Official MCP Registry

NodeMaven residential proxies: geo-targeted proxy URLs, sticky sessions, checks and usage

About

NodeMaven residential proxies: geo-targeted proxy URLs, sticky sessions, checks and usage

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.

7 files analyzed · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

API key from the NodeMaven dashboardRequired

Environment variable: NODEMAVEN_APIKEY

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-nodemaven-nodemaven-mcp": {
      "env": {
        "NODEMAVEN_APIKEY": "your-nodemaven-apikey-here"
      },
      "args": [
        "nodemaven-mcp"
      ],
      "command": "uvx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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

ToolWhat it does
proxy_urlProxy string for a country, region, city or ISP, with an optional sticky session and its lifetime. HTTP or SOCKS5.
check_proxyOpens one connection through the proxy and returns the status, the exit IP and the time it took.
list_locationsCountries, regions, cities and ISPs available for targeting, with the codes proxy_url takes.
account_statusRemaining traffic, subscription status, whether traffic is frozen.
traffic_statsTraffic used over time.
top_domainsDomains reached through the proxy, with traffic per domain.
list_sub_usersSub-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_APIKEYRequired.
NODEMAVEN_LOGIN, NODEMAVEN_PASSWORDOptional. Proxy credentials to use instead of the account's own, e.g. a sub-user.
NODEMAVEN_MCP_REVEAL_PASSWORD1 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_url returns the password as <PROXY_PASSWORD> unless NODEMAVEN_MCP_REVEAL_PASSWORD=1 is 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

Reviews

No reviews yet

Be the first to review this server!