MCP directory
Proxy Management MCP Servers: Account Tools & Access Scope
Compare MCP integrations with documented proxy-management capability, including publisher identity, credentials, tools and account restrictions.
Identify which MCP integrations expose documented proxy/account controls and what credentials those controls require.
- Does the integration manage an account or only fetch a page through a proxy?
- Which documented controls are read-only and which can change provider resources?
- Who publishes the integration, and what account credentials does it receive?
This collection covers our reviewed proxy and web-data catalog. It is not an exhaustive market survey or a performance ranking.
Category reviewed . Review due .
Compare documented requirements
4 of 4 listingsSwipe or scroll horizontally to compare requirements. Scroll back to the first column to see listing names.
| MCP server | Connection & credentials | Documented tools | Billing & restrictions | Evidence |
|---|---|---|---|---|
| Evomi MCPEvomi · official publisher Inspect Evomi proxy products, targeting and usage, rotate sessions, and run scraping jobs through a local Python MCP server. Details & setup →Provider discussionSourced JSON record | 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]
| 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. Requirements & limitations
| Documentation checkedReview due 6 source references
| |
| NodeMaven MCP (community)Artirain · community publisher An unofficial local MCP server for inspecting NodeMaven proxy targeting, fetching pages through proxies and reading account location or usage information. Details & setup →Provider discussionSourced JSON record | 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]
| 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 Requirements & limitations
| Documentation checkedReview due 9 source references
| |
| Novada MCPNovada · official publisher Search, extract pages, use browser tools and configure proxy connections through Novada’s hosted endpoint or local npm package. Details & setup →Provider discussionSourced JSON record | 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]
| 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. Requirements & limitations
| Documentation checkedReview due 6 source references
| |
| Singapore Mobile Proxy MCPSingapore Mobile Proxy · official publisher Fetch pages, check Singapore-localized Google results and inspect or rotate the provider’s mobile proxy exit through a hosted MCP endpoint. Details & setup →Provider discussionSourced JSON record | 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] | 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. Requirements & limitations
| Documentation checkedReview due 5 source references
|
How to use this comparison
Compare the documented request interface, output and account product before checking price. A JSON response can contain raw HTML; it does not by itself establish structured extraction. A browser action in one request does not by itself establish a reusable browser session.
Each row keeps the publisher’s billing basis and restrictions alongside its sources. Unknown prices or limits remain unknown. These are documentation reviews; no live connection, purchase or comparative performance test is claimed.
Overdue records remain visible with a label. This collection leaves search indexing when its category review is overdue or fewer than 3 current, visible records qualify. Individual detail pages retain their own review policy.
The collection JSON link covers the whole category before filters. It returns summaries; use each listing’s Sourced JSON record link for full sources, connections, tools and billing.
Suggest a correction · Affiliate disclosure · Collection JSON summaries