No user-submitted related servers found.
Scored across 12 tools
Most tools target clearly distinct resources/actions (search-actors vs fetch-actor-details, get-dataset-items vs get-key-value-store-record, search-apify-docs vs fetch-apify-docs). The main overlap is within the Actor introspection family (fetch-actor-details, fetch-actor-mcp-tool-list, call-actor-mcp-tool) and between search-actors and fetch-actor-details, where search results already include input fields — but descriptions clarify each purpose.
All names use kebab-case with a verb-first pattern (search-, fetch-, get-, call-, abort-, report-). The convention is fully predicable and readable across all 12 tools.
12 tools is well-scoped for a scraping platform covering discovery, execution, monitoring, storage retrieval, MCP, docs, and feedback. Each tool maps to a distinct capability in the workflow.
The core lifecycle (search → inspect → run → poll/abort → retrieve dataset/KV output) is fully covered, plus docs and MCP support. Minor gaps exist: no list-actor-runs, list-datasets, or log retrieval, so agents must rely on IDs returned from prior calls rather than enumerating resources.