NodeMaven MCP (community)

When to choose NodeMaven MCP (community)

Connect to NodeMaven MCP (community)

Choose a connection profile below and replace credential placeholders in your own MCP client. The transport describes the MCP connection.

{
  "mcpServers": {
    "nodemaven": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/Artirain/nodemaven-mcp@aaba70e5c4e882c7e1d3a75d1d61f166593449d9",
        "nodemaven-mcp"
      ],
      "env": {
        "NODEMAVEN_API_KEY": "YOUR_API_KEY",
        "NODEMAVEN_PROXY_USERNAME": "YOUR_PROXY_USERNAME",
        "NODEMAVEN_PROXY_PASSWORD": "YOUR_PROXY_PASSWORD"
      }
    }
  }
}

Inspect a route before fetching a page

A suggested sequence using the documented tools. Check the connected server's tool schema before making a call.

1. Choose supported targeting values

   Read available locations with the account API key, then choose a country and any narrower fields needed for the task.

   Tools: nodemaven_list_locations

   Sources: Pinned tool implementation, NodeMaven account API authentication

2. Check the proxy exit

   Supply the proxy username and password, then inspect the reported exit-IP result. Reduce narrow filters if the connection fails.

   Tools: nodemaven_check_proxy

   Sources: Pinned credentials and default endpoints, Pinned HTTP retrieval implementation

3. Fetch and inspect the response

   Request the page with the same targeting settings. Check status_code and truncated before using the returned text; max_bytes limits the returned body, not the total downloaded response.

   Tools: nodemaven_fetch

   Sources: Pinned HTTP retrieval implementation

Selected tools & example tasks

• nodemaven_build_proxy_url

  Build a targeting URL locally, with the password masked unless explicitly revealed.

  Example task: Prepare a location and session configuration.

  Sources: Pinned tool implementation
• nodemaven_check_proxy

  Send a proxy request to an IP information endpoint and return its reported exit details.

  Example task: Inspect the route before retrieving a page.

  Sources: Pinned tool implementation, Pinned HTTP retrieval implementation
• nodemaven_fetch

  Retrieve a URL through the proxy and return bounded text or HTML.

  Example task: Read page content from a selected exit location.

  Sources: Pinned tool implementation, Pinned HTTP retrieval implementation
• nodemaven_list_locations

  Read location choices through the account API.

  Example task: Find documented targeting values.

  Sources: Pinned tool implementation, NodeMaven account API authentication
• nodemaven_get_usage

  Read traffic, request or domain usage through the account API.

  Example task: Inspect account consumption.

  Sources: Pinned tool implementation, NodeMaven account API authentication

Troubleshoot the connection

Limits & undocumented behavior

• Community project by Artirain; not affiliated with or maintained by NodeMaven.
• Runs third-party Python code locally. The example pins the reviewed repository revision, but dependencies are resolved separately.
• Account API calls need NODEMAVEN_API_KEY; proxy requests need a separate proxy username and password.
• Page fetching performs HTTP retrieval and text conversion; it does not render JavaScript or control a browser.
• Proxy checks contact an external IP information service; requests use the provider account’s traffic.
• The URL builder masks the password by default; reveal_credentials can include it in tool output.
• Source and documentation were reviewed; the package was not installed or connection-tested.

Sources & review history

This listing is documentation-confirmed. We reviewed the primary sources below; this is not a successful live connection test.

Record updated 2026-09-27. Review due 2026-10-27.

1. Community repository and affiliation disclosureChecked 2026-09-27 · Unofficial project, local operation and credential setup.
2. Pinned package and console entrypointChecked 2026-09-27 · Python requirement, dependencies, MIT declaration and nodemaven-mcp console script.
3. Pinned stdio startup implementationChecked 2026-09-27 · Local stdio startup; client environment values override local .env values.
4. Pinned tool implementationChecked 2026-09-27 · Five MCP tool names and arguments, credential masking and targeting validation.
5. Pinned credentials and default endpointsChecked 2026-09-27 · Separate account API and proxy credentials; defaults use NodeMaven domains.
6. Pinned HTTP retrieval implementationChecked 2026-09-27 · HTTP retrieval, text conversion, truncated flag and external IP information request.
7. uv documentation: tools from Git commitsChecked 2026-09-27 · uvx --from supports a Git source pinned to a commit.
8. NodeMaven account API authenticationChecked 2026-09-27 · Account API key location, authorization format, location and statistics access.
9. NodeMaven proxy traffic billingChecked 2026-09-27 · Proxy traffic is available through pay-as-you-go and subscription plans.

Spotted a change? Share the source and the affected setup step in Site Feedback.

Alternatives to NodeMaven MCP (community)

These integrations share documented capabilities with NodeMaven MCP (community). Compare their setup and product requirements for your task.