Proxy Management MCP Servers: Account Tools & Access Scope

For this task: Read product, targeting and usage information, or change a session with rotate_proxy_session. Credential-returning tools have separate masking controls; check those before enabling the integration.[1][2]

• list_proxy_products

  Inspect account products, gateways, ports and balances.[1]

• list_proxy_targeting_options

  Find supported locations and network targeting values.[1]

• get_proxy_usage

  Read recent bandwidth consumption.[2]

• rotate_proxy_session

  Change the exit IP of a sticky session.[2]

• scrape_url

  Retrieve a page with scraping options, including documented browser mode.[1]

• search_domains

  Find domains from a search query.[2]

Scraping consumes credits according to mode and options. Proxy traffic uses the applicable product allowance. The software license does not include API usage.

Required product: Evomi Public API access plus the proxy or Scraper API product used by the tool.

For this task: Community-maintained connection building, exit checks, location and usage reads. Building a proxy URL is local configuration; it is not an account change or rotation API.[4][1]

• nodemaven_build_proxy_url

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

• nodemaven_check_proxy

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

• nodemaven_fetch

  Retrieve a URL through the proxy and return bounded text or HTML.[4][6]

• nodemaven_list_locations

  Read location choices through the account API.[4][8]

• nodemaven_get_usage

  Read traffic, request or domain usage through the account API.[4][8]

The community code is MIT licensed. Proxy requests use a NodeMaven account’s paid traffic under its current subscription or pay-as-you-go terms.

Required product: NodeMaven proxy traffic

For this task: novada_proxy produces connection settings for an external HTTP client. Some additional account writes are local-only and require confirmation; use novada_discover to inspect the available surface.[2]

• novada_setup

  Check API-key configuration and account readiness.[3]

• novada_discover

  Inspect the tools available on this connection.[2]

• novada_search

  Find pages using a search query and supported filters.[2]

• novada_extract

  Retrieve content from selected URLs.[2]

• novada_browser

  Perform documented page interactions (local stdio only; excluded from the hosted mcp.novada.com surface).[2]

• novada_proxy

  Produce proxy connection settings for an HTTP client.[2]

Scraping products draw from shared credits, with consumption depending on the product and request. Proxy plans and other product quotas can impose separate limits. Check both balance and the selected product.

Required product: Novada account with access to the scraping, browser or proxy product selected by the tool.

For this task: The documented tools inspect status and request exit-IP rotation for the Singapore service. They do not establish general country selection.[1]

• my_proxy_status

  Read the current exit, carrier and remaining quota.[1]

• fetch_url

  Fetch a URL as Markdown, text or HTML through the provider’s Singapore proxy.[1]

• search_google

  Retrieve Singapore-localized Google organic results.[1]

• rotate_ip

  Request a new Singapore mobile exit IP.[1]

MCP onboarding offers a limited trial; continued use requires the provider’s paid access. Confirm remaining quota and plan terms in the account.

Required product: Singapore Mobile Proxy MCP access and its proxy plan.