A
licenseA
qualityD
maintenanceExposes 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
TinyRex MCP
Related Servers
Alternatives to TinyRex MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server that enables running and managing file-based AI Skills, Agents, and Flow workflows as DAGs, with tools for listing, executing, and resuming tasks via stdio JSON-RPC.9MIT
- AlicenseBqualityCmaintenanceA 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.240 PyPIMIT
- FlicenseAqualityDmaintenanceMCP server that wraps MiniMax platform APIs (speech, video, image, music, and file management) as tools over stdio, enabling natural language interaction with MiniMax's AI services.161-
- AlicenseAqualityBmaintenanceAn MCP server that runs Apify scraping actors with quality-gated validation, scoring, and retries, returning embedding-ready chunks for AI agents.71MIT
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
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.