rote
Related Servers
Alternatives to rote
- AlicenseAqualityBmaintenanceAn MCP server that exposes deterministic workflows as tools, allowing small models to reliably orchestrate APIs and other MCP servers with minimal parameters.237 npm2MIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceA production-grade MCP server designed for multi-tenant, authenticated, and observable AI agent systems, enabling secure tool execution across heterogeneous data sources.67MIT
- AlicenseNot gradedqualityAmaintenanceThis MCP server provides a stateful, resettable, verifiable API runtime that gates every tool call, enabling agents to run long workflows against provider-shaped environments without live provider write access. It records decisions, side effects, and outcome evidence for replayable, verifiable benchmark runs.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceLocal MCP server that exposes fixed tools for GPT, Claude, and Gemini while routing to any OpenAI-compatible chat completions backend with independent configuration per target.1-

@spliceloom/mcpofficial
AlicenseNot gradedqualityBmaintenanceServes installed skills over stdio or Streamable HTTP and can expose 70 read-only live data tools, enabling MCP clients to discover, run, and compose verified sandboxed tools and query live Robinhood Chain, market, and DeFi data with provenance.1MIT- AlicenseNot gradedqualityCmaintenanceAn MCP server that exposes web lookup, save note, and list notes tools for a router-research-writer agent pipeline, enabling coordinated multi-agent workflows via the Model Context Protocol.MIT
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that standardizes tool discovery, execution, and context management for AI applications.MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one lists all pipelines, the other describes a single pipeline in detail. There is no overlap or ambiguity between them.
Both tools follow the same predictable pattern: `rote_` prefix followed by a verb and noun (`rote_list_pipelines`, `rote_describe_pipeline`). The convention is consistent and readable.
Only two tools are provided, which is too few for a server that can trigger pipelines and manage their lifecycle. The descriptions imply trigger, status, and signal tools exist, but they are absent, making the set severely under-scoped.
The surface only covers listing and describing pipelines, but the core operations of triggering, checking status, and sending signals are missing. This is a significant gap that will prevent agents from completing actual pipeline workflows.