mcp-guarded-tools
Related Servers
Alternatives to mcp-guarded-tools
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceGoverned MCP server for bank-grade agent tool access with RBAC, PII redaction, rate limiting, and audit logging.MIT
- AlicenseNot gradedqualityCmaintenanceAn authenticated MCP gateway that ingests documents and orchestrates hundreds of tools via progressive discovery, keeping context cost constant. It provides per-user RAG over ingested documents and a 116-tool registry that the model navigates through search, describe, and invoke tools.MIT
- AlicenseNot gradedqualityDmaintenanceA meta-server that aggregates multiple MCP servers into a single interface, reducing token usage by 98%+ through progressive tool discovery and direct code execution that processes data between tools without consuming context window space.16 npm10Apache 2.0
- AlicenseNot gradedqualityDmaintenanceToken-optimized MCP server that reduces context window usage by 59.5% by grouping 12 tools into 5 semantic operations, preserving all original functionality for AI assistants.6 npm1MIT

Context Modeofficial
AlicenseAqualityAmaintenanceAn MCP server that keeps raw tool output out of the context window by sandboxing and compressing results (about 98% reduction), persisting file edits, git operations, tasks and decisions in SQLite with BM25 retrieval so the agent resumes after compaction, and enforcing routing across 17 platforms via MCP and hooks. It also encourages the model to write scripts that compute answers and log only results instead of reading large data into context.1045,207 npm2Elastic 2.0- AlicenseNot gradedqualityFmaintenanceToken-efficient GitLab MCP server that delivers 167 tools through 3 meta-tools with progressive disclosure, field projection, server-side file trimming, and keyset pagination for agent context budgets.411 npm3MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: discovery (search_tools), inspection (describe_tool), authorization (confirm_action), and execution (invoke_tool). No overlap or ambiguity exists between their purposes.
All tool names follow the same verb_noun pattern with underscores (search_tools, describe_tool, confirm_action, invoke_tool). The naming is perfectly consistent and predictable.
With 4 tools, the set is tightly scoped for a proxy/guardian layer. Each tool earns its place and there is no bloat or missing essential step in the workflow.
The tool set covers the complete lifecycle: discovery, detail inspection, confirmation for mutations, and invocation. There are no obvious gaps; the guard mechanism is fully realized.