arsenkin-mcp
Related Servers
Alternatives to arsenkin-mcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityCmaintenanceEnables SEO analysis and data retrieval through DataForSEO API, including keyword research, backlinks, competitor analysis, and on-page audits.24-
- AlicenseBqualityBmaintenanceEnables MCP hosts to access 22 SEO Intellect API tools, handling task submission, polling, and retrieval for SEO analysis workflows.22MIT
- AlicenseDqualityDmaintenanceEnables LLMs to interact with DataForSEO and other SEO APIs through natural language, allowing for keyword research, SERP analysis, backlink analysis, and local SEO tasks.10023,858 npm82MIT
- AlicenseAqualityBmaintenanceEnables running SEO and AI/GEO visibility audits on websites, reading audit results, competitor analyses and expert reports, and importing or retrieving editorial calendars, all from any MCP client such as Claude Desktop, Claude Code or Cursor.11591 npmMIT
- AlicenseCqualityNot gradedmaintenanceEnables AI assistants to interact with DataForSEO APIs and obtain SEO data including SERP results, keyword research, on-page metrics, backlink analysis, and domain analytics through a standardized interface.7623,858 npm-
- FlicenseNot gradedqualityDmaintenanceEnables professional SEO/SEM research with geolocalized keyword discovery, competitor analysis, and SERP ranking insights using DataForSEO API.-
TDQS
Scored across 15 tools
Most tools occupy distinct workflow stages (estimate, prepare, submit, status, result, cancel), and single/batch variants are clearly labeled. A few near pairs like arsenkin_status vs arsenkin_task_status and get_result vs export_result could confuse an agent, though the descriptions do separate them.
All names share the arsenkin_ prefix and snake_case, and paired batch tools follow a clear modifier pattern. However, conventions are mixed: nouns like status and profile_catalog sit alongside bare verbs like prepare, submit, and cancel, plus get_/export_ prefixes in get_result and export_result, so the set is readable but not uniformly verb_noun.
Fifteen tools is on the upper end of a well-scoped set, but every tool addresses a distinct stage of the paid-task lifecycle, including estimates, approvals, submission, retrieval, export, and cancellation. Batch variants add count but are justified by the server's explicit batch workflow.
The core lifecycle is well covered: estimate, prepare, submit, task_status, get_result, export_result, and cancel, for both single and batch paths. The main gaps are lack of a general job-list or discovery tool and no batch-specific status/cancel endpoint, but agents can likely work around these.