nodemaven-mcp
Related Servers
Alternatives to nodemaven-mcp
No user-submitted related servers found.
Related Servers
AlicenseAqualityDmaintenanceAn MCP server enabling AI agents to drive a real browser through residential proxies with per-task geo (country/city) and sticky identity, all chosen at call time.1048 npm4MIT
scraperapi-mcp-serverofficial
AlicenseAqualityDmaintenanceA local MCP server that lets AI agents bypass bot detection, geo-restrictions, and JavaScript rendering challenges when scraping the web, backed by ScraperAPI's services285MIT- AlicenseAqualityDmaintenanceAn MCP server that gives AI agents on-demand access to proxies from the world's leading and Russian/CIS proxy providers — through a single, unified interface.11MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that lets AI agents use your real browser as an API, accessing any website with your login state, no keys or scrapers needed.1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server giving AI agents controlled residential-proxy web access with optional browser rendering and structured extraction from 60+ sites.26 PyPI1MIT

nodemaven-mcpofficial
AlicenseAqualityAmaintenanceRead-only MCP server for NodeMaven residential proxies: builds proxy URLs with country, city and ISP targeting and sticky sessions, checks a proxy and reports its exit IP, lists available locations, and shows traffic usage.1583 PyPI25MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: building a proxy URL, testing a proxy, fetching content, listing targeting locations, and retrieving usage. No two tools overlap in purpose, and the descriptions reinforce the boundaries.
All tool names follow a consistent `nodemaven_<verb>_<object>` pattern with lowercase snake_case. Verbs (build, check, fetch, list, get) are distinct and predictable, making the set easy to navigate.
The server has 5 tools, which is well-scoped for a proxy management domain. Each tool earns its place, covering the essential operations without unnecessary bloat or redundancy.
The tool set covers the full proxy lifecycle: discover targeting options, construct a proxy URL, verify it works, fetch content through it, and monitor usage. There are no obvious dead ends or missing critical operations.