Skip to main content
Glama
sahilrit

openactors

by sahilrit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to openactors

No user-submitted related servers found.

    Related Servers

    • wigolo

      CraftArt
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to perform local-first web search, fetch, crawl, extract, cache, research, and autonomous information gathering through MCP, with no API keys or cloud dependencies.
      813 npm
      AGPL 3.0

    • mcp-apify

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables running Apify Actors for web scraping and automation, fetching dataset results, and scraping URLs to clean markdown via MCP.
      215 npm
      MIT

    • Shark-no-Kari

      HaiNick
      A
      license
      Not graded
      quality
      B
      maintenance
      Remote MCP server for web scraping with anti-bot evasion. Provides stealth HTTP fetching, headless browser with Cloudflare bypass, CSS selectors, YouTube transcripts, and Markdown conversion.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivityMaintained
    ResponsivenessNo issues

    Resources