Skip to main content
Glama
Sign In
TinyRex MCP

TinyRex MCP

by emirmrkaljevic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to TinyRex MCP

No user-submitted related servers found.

    Related Servers

    • actors-mcp

      fecklesspleb
      A
      license
      A
      quality
      C
      maintenance
      MCP server that exposes 14 fecklesspleb Apify Actors (job boards, Hacker News, SEO audit, metadata, web tools) as tools; runs bill per result to the caller's own Apify account.
      10
      433 npm
      MIT

    • veriloop

      arvindcr4
      A
      license
      A
      quality
      D
      maintenance
      Exposes a verified tool registry (calculator, sandboxed file read, web fetch) over MCP stdio, enabling any MCP-capable client to reuse the same tools from the inspectable ReAct loop.
      3
      MIT

    • Apify MCP server

      clanker25
      A
      license
      Not graded
      quality
      C
      maintenance
      Gives AI agents access to thousands of ready-made Apify Store Actors, letting them search for a tool, inspect its input and pricing, run it, and read back structured results for web scraping, data extraction, and browser automation. It can be used as a hosted endpoint with OAuth or run locally over stdio.
      41,000 npm
      MIT

    • AgentTasker MCP Server

      S3bRR
      A
      license
      B
      quality
      C
      maintenance
      A lightweight stdio-only MCP server that allows AI agents to run multiple tasks (e.g., Python code, HTTP requests, shell commands) in parallel or with dependencies, returning structured results in a single call.
      2
      47 PyPI
      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.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: list_actors for discovery and run_actor for execution. There is no overlap, and the descriptions explain their relationship through the exampleInput field.

    Naming Consistency5/5

    Both names follow a consistent snake_case verb_noun pattern: list_actors and run_actor. The verbs are distinct and the noun is consistent.

    Tool Count3/5

    Only two tools are provided, which is below the typical 3-15 range and may feel thin for a server that might need run management. However, for the narrow scope of discovering and running actors, it could be sufficient.

    Completeness4/5

    The surface covers actor discovery and execution, including example inputs and result retrieval. However, it lacks operations for managing runs (e.g., status, cancellation, or retrieving past runs), which agents might need for long-running or async actors.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Resources