Skip to main content
Glama
vorionsys

@vorionsys/mcp-server

Official
by vorionsys
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to @vorionsys/mcp-server

No user-submitted related servers found.

    Related Servers

    • gov-mcp

      liuhaotian2024-prog
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enforces runtime governance on AI agent actions — file access, command execution, delegation chains, and permission escalation.
      MIT

    • Maple

      alnosarus
      F
      license
      Not graded
      quality
      D
      maintenance
      A unified MCP server providing observability, safety control, and behavior evolution for high-agency AI agents through tracing, replaying, and auditing. It features real-time firewall guardrails and ML-driven anomaly detection to monitor, block, or fork agent actions based on risk.
      2 npm
      -

    • a2a-trustgate

      jyswee
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for AI agent compliance that screens actions before execution and records decisions in an immutable, SIEM-ready audit trail.
      49 npm
      -

    • agent-security-gateway

      Un1u6ky
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides a security gateway for AI agents, enforcing allow/confirm/deny policies on tool calls and requiring human approval for risky operations, with full audit logging.
      -

    • governed-mcp

      rsiraj0
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enforces governance on agentic decisions with auditable evidence records, providing tools for understanding, calibrating confidence, and navigating handoffs based on policy.
      1
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool targets a distinct action within the governance domain, but vorion_execute_governed composites several other tools (gate, signal, log), which could create slight overlap. Descriptions are clear enough to disambiguate intended usage.

    Naming Consistency3/5

    All tools share the vorion_ prefix and snake_case, but ordering mixes verb-first (check_trust, record_signal) with noun-first (tenant_list, canary_submit). This is a moderate inconsistency that remains readable.

    Tool Count5/5

    10 tools is well within the ideal 3-15 range, and each tool covers a necessary aspect of the governance system without unnecessary bloat.

    Completeness4/5

    The set covers core governance workflows: trust checks, signal recording, gating, logging, execution, tenant context, audit, canary, and health. Minor gaps like direct agent CRUD exist but are not essential to the stated purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources