rumors-lines-mcp
Related Servers
Alternatives to rumors-lines-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMultilingual sentence corpus MCP server. Enables search, retrieval, and translation of sentences across many languages.1 npmMIT
- AlicenseAqualityBmaintenanceMCP server exposing quote and live cryptocurrency price tools, with both local (stdio) and cloud-deployed (HTTP) transports.2MIT
- AlicenseNot gradedqualityCmaintenanceA minimal MCP server that tells an interactive knock-knock joke suitable for children, supporting both local stdio and HTTP deployments.78 npmISC
- FlicenseNot gradedqualityCmaintenanceA minimal MCP server over Streamable HTTP demonstrating the MCP protocol with tools for health checks, echo, and text reversal.-
- AlicenseNot gradedqualityDmaintenanceA lightweight MCP server empowering LLM clients with Indic language processing: translation, transliteration, language identification, and chat with Sarvam AI models.MIT
- AlicenseBqualityBmaintenanceA lightweight, dependency-free MCP server that answers cited queries over a Tero corpus index.json via stdio JSON-RPC 2.0, with honest refusal semantics and no silent empty results.9MIT
TDQS
Scored across 4 tools
Each tool has a distinct action: list_collections enumerates collections, get_lines retrieves lines for a given collection URL, random_line returns a single random line with optional filters, and search_lines performs substring search. The overlap between get_lines and search_lines is minimal because get_lines requires a collection URL while search_lines searches across all lines; an agent can easily choose.
All names use snake_case and are readable, but random_line breaks the verb_noun pattern used by list_collections, get_lines, and search_lines by using an adjective instead of a verb. This is a minor deviation from an otherwise consistent convention.
Four tools are well-scoped for a read-only pick-up line browsing service: discover collections, fetch lines, get a random line, and search. No tool feels redundant or missing for the core purpose.
The read-only surface covers listing, fetching, random sampling, and text search, which are the primary workflows. Minor gaps include no pagination for large collections or search results and no explicit way to discover available languages/registers beyond collection language metadata, but agents can work around these.