A
licenseA
qualityA
maintenanceMCP server for agent-friendly web scraping with adaptive anti-bot bypass, dynamic rendering, and structured data extraction via 12 tools.
12
MIT
Evomi MCP Server
Officialby evomi
Related Servers
Alternatives to Evomi MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server providing tools for web scraping, browser automation, computer vision, audio transcription, and RAG via API.91MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for multi-engine browser automation with proxy rotation, enabling AI-driven web interaction and task execution across Camoufox, DrissionPage, and Browser Use.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server for web scraping and browser automation, enabling AI agents to extract clean, token-efficient content from web pages.1MIT
- AlicenseBqualityDmaintenanceMCP server for the Spider web crawling and scraping API, enabling AI agents to crawl, scrape, search, and extract web data.13282MIT
aethyn-browser-mcpofficial
AlicenseAqualityCmaintenanceAn 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.10633MIT
TDQS
B3.1/5.0
Scored across 39 tools
Disambiguation3/5
Most tools are organized by resource and have distinct purposes, but agent_request intentionally overlaps with every other operation by being able to 'do ANY Evomi operation'. The proxy credential/connection-string tools also overlap and rely heavily on detailed descriptions to avoid misselection.
Naming Consistency4/5
The vast majority of tools follow a consistent verb_noun snake_case pattern: list_configs, create_schedule, get_proxy_credentials, rotate_proxy_session. The one clear outlier is agent_request, which is noun-like rather than an imperative verb, preventing a perfect score.
Tool Count2/5
With 39 tools, the server is well past the 25-tool threshold for an agent-friendly surface. The count is inflated by multiple parallel CRUD families plus several proxy-related generators and builders, making tool selection harder even though the domains are related.
Completeness3/5
Core scraping and proxy lifecycle coverage is strong: scrape/crawl/map, configs, schemas, schedules, proxies, and account info are all represented. However, storage configs lack a get_storage_config, browser profiles only have a list operation, and async tasks have no cancellation or history listing, so some workflows dead-end.
Maintenance
ActivityMaintained
ResponsivenessNo issues