Skip to main content
Glama
arian-gogani

nobulex-mcp-server

by arian-gogani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to nobulex-mcp-server

No user-submitted related servers found.

    Related Servers

    • Nobulex MCP Compliance Server

      arian-gogani
      A
      license
      A
      quality
      C
      maintenance
      Provides covenant rule enforcement, hash-chained audit logs, and integrity verification for MCP-compatible agents. It enables users to define granular permission rules and maintain a tamper-evident audit trail of all actions.
      4
      11 npm
      1
      MIT
    • mcp-vaara by vaaraio

      mcp-vaaraofficial

      vaaraio
      A
      license
      Not graded
      quality
      A
      maintenance
      Gates every AI agent tool call against your policy before it runs, then writes a hash-chained, tamper-evident record of what was decided and what happened. Anyone can verify that record offline, without your software, your systems or any key you hold.
      13
      AGPL 3.0

    • mcp-audit-gateway

      elang2
      A
      license
      Not graded
      quality
      A
      maintenance
      Tamper-evident audit trail for AI agent tool calls. Cryptographically signed, hash-chained records that prove what your agents did.
      3
      47 npm
      MIT

    • Dvarapala

      demolished-lab
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides permission gates and tamper-evident audit logging for AI agent tool executions, with declarative policies, consent ladders, and hash-chained verification.
      MIT
    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

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: checking actions, retrieving audit logs, setting rules, and verifying log integrity. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (check_action, get_audit_log, set_rules, verify_log).

    Tool Count5/5

    Four tools is an appropriate scope for a compliance/auditing server; each tool serves a necessary function without redundancy.

    Completeness4/5

    Covers core operations: rule setting, action checking, audit log retrieval, and log integrity verification. Minor gap: no explicit rule deletion or modification beyond full replacement, but this is acceptable for the domain.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources