aperion-shield
OfficialRelated Servers
Alternatives to aperion-shield
- AlicenseAqualityAmaintenanceNode.js server implementing Model Context Protocol (MCP) for filesystem operations.1014497,862 npm90,569-
- AlicenseAqualityDmaintenanceA Postgres MCP server with index tuning, explain plans, health checks, and safe sql execution.10MIT
- AlicenseBqualityAmaintenanceSelf-hosted GitHub MCP server for PR, repo file, and Dependabot operations, supporting multiple MCP clients with personal access token auth.7MIT
Related Servers
- AlicenseNot gradedqualityBmaintenanceSecurity scanner and runtime proxy for MCP servers. Catches tool poisoning, prompt injection, and rug-pull attacks (silent tool description changes) before they reach your AI agent. Includes a static scanner and a runtime stdio proxy.59 npmMIT
- AlicenseNot gradedqualityAmaintenanceGuardrail sidecar proxy between AI agents and their MCP/REST/CLI tools. Policy engine, human approval gates, time-limited grants, rate limiting, and OTEL tracing. One Go binary, one YAML config, fail-closed by default.1Apache 2.0

SentinelGateofficial
AlicenseNot gradedqualityAmaintenanceOpen-source MCP proxy that enforces security policies, content scanning, and audit logging between AI agents and tool servers25AGPL 3.0- AlicenseNot gradedqualityDmaintenanceRuntime safety guardrails for AI coding agents. Checks file access, validates shell commands, and scores your repo's AI safety — all via MCP.4 npm8MIT
- AlicenseAqualityAmaintenanceEnables sub-millisecond pre-execution safety filtering for AI agent tool calls, blocking destructive shell commands, dangerous SQL mutations, credential access, SSRF, and scope-creep or prompt-injection patterns before they execute, with optional fail-closed transparent proxy wrapping for any MCP server.651 npm1Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA defensive gateway and firewall for AI agents using MCP servers, scanning tool calls, responses, and manifests for prompt injection, secrets, dangerous commands, and drift before allowing execution.MIT
TDQS
Scored across 14 tools
Most tools target distinct file operations, but read_file is a deprecated duplicate of read_text_file and list_directory overlaps heavily with list_directory_with_sizes, creating avoidable ambiguity. directory_tree also offers a third way to inspect directory contents, though its recursive JSON output is distinct enough.
The set overwhelmingly follows a clear verb_noun snake_case pattern (read_text_file, write_file, create_directory, move_file, get_file_info). directory_tree is a minor deviation since it lacks a verb, but this does not seriously impair predictability.
14 tools is a reasonable size for a filesystem-oriented server, but a couple of tools are redundant (deprecated read_file and list_directory_with_sizes vs. list_directory). Slightly trimming duplicates would make the count tighter, but the overall scope is appropriate.
Read, write, edit, move, create, search, and metadata operations are covered, but there is no delete_file/remove_directory or copy operation, leaving lifecycle coverage incomplete. Agents performing file cleanup or duplication tasks would hit a dead end.