embrace-raw-readonly
Related Servers
Alternatives to embrace-raw-readonly
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables MCP-compatible hosts such as OpenCode to drive the Codex CLI through codex app-server over stdio, exposing tools to run prompts, inspect status, list threads, and interrupt running turns.-
- AlicenseBqualityBmaintenanceEnables diagnosing, testing, benchmarking, and deliberately controlling LM Studio through a local-only MCP stdio server, with mutations disabled by default and evidence-based capability verification.18MIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients such as Claude Desktop or Claude Code to drive the local daemon through stdio, listing agents and sessions, running agents, and reporting costs.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to read Sierra Chart study outputs, chart discovery, and study metadata/history via read-only tools over Streamable HTTP or stdio.MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to connect to Agenzax's REST API over stdio, providing tools for messaging, session management, and review-mode oversight.18414 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to discover and execute operational tools such as database mutations and system diagnostics over stdio, with deterministic structured outputs and Langfuse observability.-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one lists available tools, the other invokes a specific tool. There is no overlap or ambiguity in selecting between them.
Both tools start with 'embrace_' and include 'readonly', but one is 'list_readonly_tools' (verb_noun) while the other is 'call_readonly' (verb_adjective). The pattern is mostly consistent but not perfectly parallel.
With only two tools, the surface is thin. However, this is a deliberate thin proxy layer for a remote readonly API, so the minimalism is justified, but it still falls below the typical well-scoped range.
The two tools form a complete interface for interacting with the remote readonly toolset: listing available schemas and calling them. There are no missing operations within the stated scope of acting as a proxy.