No user-submitted related servers found.
Scored across 10 tools
The SEO trio (audit vs. metadata extract vs. sitemap) is clearly delineated, with descriptions explicitly cross-referencing each other ('use extract_website_metadata instead when you only need the tags'). The job family is murkier: ats_jobs overlaps directly with greenhouse_jobs, lever_jobs, ashby_jobs and workday_jobs, and only the 'use it when you have a mix of companies or do not know which ATS' phrasing keeps the boundary inferable. search_hacker_news also bundles two unrelated modes (keyword search vs. whoIsHiring job parsing) into one tool.
Two patterns coexist: verb_noun for the web tools (seo_audit_website, extract_website_metadata, extract_sitemap_urls) and search_* for two more, but the job tools are bare noun phrases (greenhouse_jobs, lever_jobs, workday_jobs, ats_jobs) with no verb. Names are readable and snake_case throughout, but the verb-first vs. resource-first split is inconsistent. The server name 'actors-mcp' also signals nothing about the SEO/jobs split.
Ten tools is a well-scoped set, and each one maps to a concrete Apify Actor with a real purpose rather than filler. The per-vendor job scrapers are redundant-ish but each targets a genuinely different source API.
The SEO side covers discovery (sitemap), diagnosis (audit) and per-URL metadata extraction, which is a coherent lifecycle with no obvious dead end. The jobs side covers major ATS vendors plus an aggregator and remote feeds, but has no follow-up tool to fetch a single job's full detail later (you must re-run with includeDescription) and no cross-tool aggregation of the vendor results.
