GuardRails-MCP
Related Servers
Alternatives to GuardRails-MCP
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables AI coding clients to inspect and invoke local-only tools for an evidence-gated outbound workflow, including buyer selection, mailbox verification, deduplication, factual preflight, and approval-hash checks, with sending disabled by default. It supports synthetic demos and dry-run transports without mailbox credentials, while requiring explicit authorization before any live email action.MIT- AlicenseAqualityBmaintenanceLets an assistant read recorded production AI agent runs — steps, model and tool calls with arguments, and outcomes — along with the findings of comparison runs that checked a prompt or model change against those recordings, and verify a signed evidence bundle offline with no account or network. It is strictly read-only: no tool starts a replay or comparison, so nothing can spend money or act without a person deciding.519 PyPIApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables local, read-only analysis of Codex and Claude Code conversations through ten MCP tools for browsing sessions, inspecting tokens and tools, and comparing sessions without accounts or cloud services.1PolyForm Noncommercial 1.0.0

Zof MCP serverofficial
AlicenseNot gradedqualityAmaintenanceGives a compatible coding agent read-only access to bounded local verification of changes inside a single host-chosen workspace, exposing six stdio tools that inspect capabilities, static checks, impact analysis, policy evaluation, evidence generation, and suggested tests without shell access, plugin loading, or repository upload.35 npmApache 2.0- AlicenseNot gradedqualityAmaintenanceEnables AI agents to analyze, cluster, compare, and export reports from local log files through seven read-only tools, returning compact evidence packs with line-number citations instead of raw log dumps. All processing happens on the local machine, so log data never leaves the environment.135 PyPI1MIT
- AlicenseNot gradedqualityCmaintenanceExposes four stdio tools that let an agent research an application's documented interface, produce a validated single-use plan, and execute read-only operations against public HTTP JSON APIs, static HTML/JSON/text sources, and host-configured CLIs. Runs in-process with no listening port, accounts, or model dependency, returning bounded results while keeping inputs and outputs inside a host-enforced research-plan-execute lifecycle.MIT
TDQS
Scored across 4 tools
Each tool targets a distinct resource and action: list_cases covers fixed cases, run_demo creates a run, list_runs lists existing runs, and get_run retrieves a specific run. There is no overlap or ambiguity in selecting the right tool.
All tool names use snake_case and follow a verb_noun pattern: list_cases, run_demo, list_runs, get_run. The convention is consistent and predictable throughout.
Four tools are well-scoped for a focused evaluation/demo server. Each tool earns its place by covering a core operation without redundancy or bloat.
The surface covers the essential lifecycle: listing cases, running a demo, and inspecting runs. Minor gaps exist, such as no way to delete or clean up runs and no individual case retrieval, but these are likely workarounds for the stated demo purpose.