openrhyme-mcp
OfficialRelated Servers
Alternatives to openrhyme-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP-capable AI clients to control a local computer over stdio with filesystem operations, ripgrep search, shell command execution, and persistent process sessions.14MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to search, record, correct, and review the provenance and version history of memories, and to obtain answers composed from guarded context in which private values are replaced by placeholders and resolved locally on the device. Exposes these capabilities through dependency-free tools over stdio.MIT
- AlicenseNot gradedqualityCmaintenanceEnables local, source-traceable retrieval over prepared chat history and, only with separate authorization, AI-simulated persona conversations through a stdio MCP interface.MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP stdio bridge that lets compatible agents query a local, provenance-first memory graph, fetch source-versioned text, inspect retrieval, check service health, and report usefulness feedback.1MIT
- AlicenseNot gradedqualityDmaintenanceProvides a stdio MCP bridge for coding agents to query and record engineering knowledge locally, preserving debugging history, failed attempts, and verified solutions.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI agents to store, search, link, and retrieve encrypted long-term memories through a local stdio interface, with bounded graph exploration and context assembly.12GPL 3.0
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: events queries captured activity data, status reports engine/server state, apps lists the allowlist and running apps, and allow_app/deny_app make targeted allowlist changes. There is no functional overlap between any of these tools.
The read-only tools use noun-style names (events, status, apps) while the mutations use verb_noun style (allow_app, deny_app). This is fairly predictable and readable, though not as uniform as a single verb_noun convention throughout.
Five tools is well-scoped for this server's purpose: querying activity events, checking engine status, listing apps, and managing the allowlist. Each tool earns its place without the surface feeling bloated or thin.
The core workflows are fully covered: retrieve activity data, inspect engine health, view the allowlist, and add or remove apps from it. Since events are an append-only raw log, update/delete operations are not expected here, so there are no obvious gaps.