aparser-mcp
Related Servers
Alternatives to aparser-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with the Apify platform to manage actors, monitor runs, and retrieve scraped data from datasets. It supports natural language commands for executing web scrapers, managing tasks, and accessing key-value stores.28MIT
- AlicenseAqualityCmaintenanceEnables AI agents to retrieve competitor Google ads, app reviews, job postings, PDF tables, bank statement and invoice data, clean email lists, capture website screenshots, and find broken links through Apify-backed tools.14MIT

georanker-seo-mcpofficial
AlicenseAqualityBmaintenanceEnables AI assistants to search Google SERPs, track rankings across locations, run Lighthouse SEO audits, find broken internal links, analyze backlinks, and get keyword volume data through a hosted service.1516 npmMIT- FlicenseAqualityBmaintenanceEnables SEO task management, including estimating, submitting, and monitoring jobs, retrieving results, and exporting CSV/JSONL data.181-
- AlicenseNot gradedqualityCmaintenanceGives AI agents live search data over Streamable HTTP: Google and Bing results with AI Overview citations, keyword volume/difficulty, ranked keywords, competitor gaps, backlinks and referring domains, plus single-page SEO audits. Also exposes a pass-through for any other DataForSEO v3 endpoint, billed per call.285 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to pull Google and Yandex search results, Wordstat keyword expansions and demand history, and a site's ranking positions by phrase, region, and device, plus account balance checks. It also supports batch position runs with caching, history, and CSV updates.MIT
TDQS
Scored across 10 tools
Each tool targets a distinct concern: health (ping), server status (info), parser discovery (list_parsers), schema introspection (parser_info), proxy access (get_proxies), synchronous execution (one_request), and async task lifecycle (add_task, task_state, wait_task, task_results). Even task_state and wait_task differ clearly: one returns a snapshot, the other blocks until completion.
Task operations mostly use a task_ prefix (add_task, task_state, wait_task, task_results) and parser operations pair list_parsers with parser_info. However, the mix of verb-first names (add_task, get_proxies) and resource-first names (task_state, parser_info), plus the outlier one_request, prevents a perfect score.
With 10 tools, the set is well-scoped for a parsing automation server. Every tool serves a clear role in the workflow—health, info, discovery, schema, proxies, single request, task submission, monitoring, and retrieval—with no redundancy or bloat.
The surface covers the full lifecycle: health check, server status, parser listing and schema introspection, proxy management, synchronous one-off parsing, bulk task submission, monitoring (both snapshot and blocking), and result retrieval. No critical operation is missing for typical usage.