@palveron/mcp-server
Related Servers
Alternatives to @palveron/mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides a governance layer for MCP servers, enforcing policy-based allow/deny/approval rules, requiring human approval for risky calls, and recording an auditable trail of every AI agent tool call.MIT
- FlicenseNot gradedqualityBmaintenanceProvides a secure MCP boundary for AI agents, intercepting and validating tool calls, redacting secrets, and requiring human approval for sensitive actions with a tamper-evident audit trail.-

authensor-mcp-serverofficial
AlicenseNot gradedqualityCmaintenancePolicy enforcement gateway for MCP tool calls, evaluating every tool invocation against declarative YAML policies (allow/deny/escalate-to-human), generating cryptographic hash-chained audit receipts, and including built-in content safety scanning.2MIT- AlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP clients to route every tool call through configurable rules that allow, block, or hold risky actions for human approval, while recording decisions in a tamper-evident audit trail.Apache 2.0

ERDL Guardofficial
AlicenseNot gradedqualityAmaintenanceEnforces deterministic policy decisions on AI agent tool calls, supporting allow, deny, correct, escalate, and human review actions with verifiable audit receipts.12 npmMIT- AlicenseNot gradedqualityBmaintenanceEnforces configurable policies on AI agent tool calls, allowing, requesting review, or denying actions before they are executed.MIT
TDQS
Scored across 3 tools
Each tool has a distinct purpose: palveron_check verifies a single action, palveron_status provides system diagnostics, and palveron_policy_list lists policies. There is no ambiguity or overlap between them.
All tools share the consistent palveron_ prefix and snake_case format, but the second word is a mix of verb (check) and nouns (status, policy_list). Minor deviation from a strict verb_noun pattern.
Three tools is well-scoped for a governance checker: one to perform checks, one for status, and one for policy listing. No tools feel redundant or missing.
The domain is governance policy enforcement, and the set covers the core operations: enforcing a policy (check), understanding system state (status), and discovering applicable policies (list). No obvious gaps for the stated purpose.