reasongate
Related Servers
Alternatives to reasongate
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables developers to wrap existing MCP servers with a deterministic policy enforcement gate that intercepts tool discovery and tools/call requests over stdio, allowing only authorized calls to reach the downstream server. It supports dynamic tool exposure or hiding, allow/deny/approval-required decisions, configurable error disclosure modes, and Ed25519-signed retry credentials for approved workflows.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceSelf-hosted MCP gateway that applies deterministic, compiled policy to tool discovery, invocation, and outbound data flow, with no model in the enforcement path. Every decision emits a hash-chained receipt sealed with Ed25519 and verifiable using public keys only.Apache 2.0

aperion-shieldofficial
FlicenseAqualityAmaintenanceLocal guardrail proxy for AI coding agents. Wraps any MCP server (stdio or HTTP/SSE) and blocks destructive tool calls before they execute, with TOFU catalog pinning against rug pulls and tool-poisoning/result-injection scanning. Single Rust binary, Apache-2.0.1411-- AlicenseBqualityCmaintenanceSecurity gateway that wraps any MCP server with per-tool policies, approval gates, and optional Ed25519-signed decision receipts. Shadow mode logs every tool call without blocking; enforce mode applies block, rate-limit, and minimum-tier rules. Receipts are independently verifiable offline with no accounts needed.51,760 npm10MIT
- AlicenseNot gradedqualityAmaintenanceSecurity gateway for MCP servers. Wraps any MCP server with per-tool policies (Cedar + JSON), Ed25519-signed decision receipts, human approval gates, and trust tiers. Shadow mode by default — logs everything, blocks nothing.1,760 npm9MIT
- AlicenseNot gradedqualityCmaintenanceSits in front of any MCP server to enforce allow/ask/block policies on tool calls, paths, shell commands, and network domains, with local approval prompts and an audit log.MIT
TDQS
Scored across 14 tools
Several tools overlap significantly: read_file is redundant with read_text_file despite being deprecated, read_multiple_files overlaps with read_text_file, and list_directory and list_directory_with_sizes differ only by added size output. An agent could easily select the wrong tool for a simple read or listing task.
Most tools follow a consistent verb_noun snake_case pattern (write_file, read_text_file, create_directory, search_files), making the set predictable. Minor deviations like directory_tree and the deprecated read_file add slight ambiguity, but there is no mixed casing.
14 tools is a reasonable size for a filesystem server, but the presence of a deprecated read_file and duplicated listing tools makes the count feel slightly inflated. Still, the overall scope is manageable and not excessive.
The toolset covers create, read, edit, move, list, search, and metadata operations, but lacks delete_file, delete_directory, and copy operations—core filesystem actions. Agents needing to remove or duplicate files or directories will hit a dead end, leaving significant lifecycle gaps.