No user-submitted related servers found.
Scored across 44 tools
Seven job-related tools (find_hiring_companies, get_company_jobs, find_remote_jobs, search_startup_jobs, search_tech_jobs, search_indeed_jobs, search_naukri_jobs) overlap heavily, and contact-finding is scattered across find_local_businesses, find_website_contacts, analyze_shopify_stores, get_trade_show_exhibitors and search_podcasts. Research (analyze_field, validate_idea, search_research) and company data (find_companies, search_import_records, search_startup_funding) also blur together. Descriptions help, but an agent must read the full text to pick correctly.
All 44 names use snake_case with a verb_noun structure, which is predictable and readable. The only weakness is inconsistent verb choice for similar retrieval operations (find_ vs search_ vs get_ used interchangeably across job, company and contact tools).
44 tools is far too many for a single server and reflects a grab-bag of unrelated domains (jobs, property, biotech, sports, lottery, sanctions). Each tool is a thin wrapper over one Apify actor rather than part of a coherent, scoped surface.
Coverage is broad across many verticals, but each domain gets only one or two read-only scrapers with no lifecycle operations, and there is no tool for run management, spend/budget inspection, actor listing or a generic fallback runner. Agents can work around gaps but may hit dead ends when a needed source is absent.
