mcp-server-patterns
Related Servers
Alternatives to mcp-server-patterns
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables external MCP clients to invoke governed tools with schema validation, budgets, policy checks, human approval for side-effecting actions, and prompt-injection quarantine.MIT
- FlicenseNot gradedqualityCmaintenanceEnables MCP tool calls with strict schema validation and stdio isolation, while providing a security gateway for tool-level authorization, streaming PII redaction, and model failover routing.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to safely call MCP tools through a security gateway that enforces per-role authorization and least-privilege tool scoping.1-
- AlicenseNot gradedqualityBmaintenanceProvides a single MCP endpoint that dynamically discovers, routes, policy-checks, and executes hundreds of MCP tools from any agent, with optional LLM-based routing.19 npm1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to access upstream MCP capabilities and OpenAI-compatible model routes through one invariant-preserving, policy-bounded endpoint with deterministic routing, leases, durable Tasks/Runs, and verifiable outcomes.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables LLM agents to safely invoke enterprise MCP tools under an enforceable guard that applies allowlist policies, caller roles, parameter restrictions, human confirmation for destructive operations, and a correlated JSONL audit log.43 PyPIAGPL 3.0
TDQS
Scored across 15 tools
Each tool targets a clearly distinct resource/action: table inspection, job lifecycle, cluster lifecycle, model listing/invocation, workspace listing, and vector search. Tools like list_tables, describe_table, and sample_table are related but have unambiguous distinctions, and no two tools appear to do the same thing.
Nearly all tools follow a consistent snake_case verb_noun pattern, and singular/plural resource naming is used conventionally. The only mild deviation is vector_search, which follows a noun_verb form but remains clear and readable.
The server exposes 15 tools, which is at the upper end of the ideal range but still well-scoped for a data-platform control surface. Each tool maps to a meaningful operation across tables, jobs, clusters, models, workspaces, or search.
Core operational coverage is present for listing, inspecting, running/canceling jobs, starting/terminating clusters, and invoking models. However, there are notable gaps such as creating/altering tables, detailed get operations for clusters/models/workspaces, and model deployment/update workflows.