{"id":"ryanjoachim-mcp-batchit","name":"mcp-batchit","af_score":55.8,"security_score":21.2,"reliability_score":26.2,"what_it_does":"mcp-batchit is an MCP “aggregator” server that exposes a single tool, `batch_execute`, to batch multiple downstream MCP tool calls into one JSON-RPC request. It spawns/connects to a target MCP server (e.g., filesystem) and runs sub-operations in parallel up to `maxConcurrent`, with per-op `timeoutMs` and optional `stopOnError` behavior, returning a consolidated result array.","best_when":"When you have many MCP tool calls that are independent (or can be done in phases) and want to reduce message overhead/tokens by executing them as a single `batch_execute` request.","avoid_when":"When sub-operations are order-dependent on outputs from earlier sub-operations, or when you require strong security guarantees around file/network access beyond what the downstream MCP server enforces.","last_evaluated":"2026-03-30T15:19:56.790290+00:00","has_mcp":true,"has_api":false,"auth_methods":[],"has_free_tier":false,"known_gotchas":["BatchIt does not support data passing between sub-operations within the same request (multi-phase calls are required).","If `transport` is configured to point to the aggregator instead of the intended downstream MCP server, you may see “tool not found.”","Partial results are returned; with `stopOnError=true`, remaining sub-ops are skipped while already-running ones may finish.","Concurrency can cause ordering assumptions to fail if the downstream tools are not safe for parallel execution.","Aggregation spawns downstream servers via `npx` in the example; ensure your runtime environment and supply chain controls are appropriate."],"error_quality":0.0}