F
licenseNot graded
qualityB
maintenanceEnables local-first web scraping and captcha solving via an MCP server written in Rust.
-
openactors
by sahilrit
Related Servers
Alternatives to openactors
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to perform AI-powered web scraping, extraction, search, crawling, schema generation, and scheduled monitor management through local or hosted integration.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to scrape web pages, extract structured data, search, crawl sites, generate schemas, schedule monitors, and inspect credits/history through hosted or local integrations.-
anyapi-mcpofficial
AlicenseAqualityBmaintenanceLocal stdio MCP server for AnyAPI - hundreds of scraping and data APIs behind one key, priced per request in USD.1044 npm1Apache 2.0- AlicenseNot gradedqualityDmaintenanceEnables web scraping, browser automation, and dataset management through Apify's actor platform.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search the web through configured providers and crawl individual pages or entire sites into clean Markdown or JSON, including authenticated browsing and deduplicated output. It can run locally over STDIO or HTTP and integrates with MCP clients and command-line workflows.-
TDQS
A3.6/5.0
Scored across 26 tools
Disambiguation4/5
Tools are grouped into clear clusters—actors, runs, tasks, datasets, schedules, and job tracking—and each tool targets a distinct resource and action. A few pairs like call-actor vs run-actor-task and mark-job vs record-response are somewhat close, but their descriptions clearly separate them.
Naming Consistency4/5
Most tools follow a lowercase hyphenated verb-noun pattern, which is readable and mostly predictable. There are minor inconsistencies such as fetch vs get, call vs run, clean-up vs delete, and list naming varies (get-actor-run-list vs get-actor-task vs get-schedules).
Tool Count2/5
At 26 tools, the set is over the 25-tool threshold and feels heavy for an agent to navigate. The actor, dataset, schedule, and job-tracking concerns are broad enough that the server may be trying to cover too much in one surface.
Completeness4/5
The set covers actor discovery, execution, run inspection, saved tasks, datasets, schedules, storage access, and job follow-up workflows with no obvious dead ends. Minor gaps exist: key-value store access is read-only and there is no individual dataset deletion, though clean-up-storage partially covers cleanup.
Maintenance
ActivitySlowing
ResponsivenessNo issues