Skip to main content
Glama

Related Servers

Alternatives to @lucairn/mcp-server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Security middleware for LLM apps and AI agent pipelines. Detects prompt injection attacks (22 signatures, 7 languages) and anonymizes PII (17 entity types). Deterministic, sub-25ms, GDPR Art.30 compliant.
      -
    • A
      license
      A
      quality
      A
      maintenance
      Self-hosted governance layer between an AI assistant and your data: allow/deny policy, deterministic PII masking, row caps, and a hash-chained audit log with an Ed25519-signed receipt for every access, verifiable offline.
      4
      561 npm
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides cryptographic signing and verification for AI decisions to generate verifiable, Ed25519-signed receipts for compliance and auditing. It automatically maps AI actions to regulatory frameworks like HIPAA and SOX with high-performance, sub-3ms signing.
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Bounded egress gateway & secret proxy for AI agents and applications, enabling safe credential injection into upstream requests while keeping raw secrets out of LLM prompt contexts.
      8 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides a pre-flight/post-flight firewall for LLM calls with comprehensive detection, classification, policy enforcement, reversible redaction, output safety, and immutable audit logging.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Third-party certifying proxy — sign any HTTP call (AI agents, webhooks, microservices) with an independent Ed25519 signature, RFC 3161 timestamp, and Sigstore Rekor anchor.
      4
      1,210 PyPI
      2
      MIT

    TDQS

    A4.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguous selection. The single tool clearly defines its action and scope, so agents cannot confuse it with anything else.

    Naming Consistency5/5

    The sole tool name, `chat_via_lucairn`, follows a clean snake_case verb-phrase convention. There are no other names present, so there are no conflicting naming styles to navigate.

    Tool Count4/5

    One tool is slightly below the typical 3–15 tool range, but it is a substantial operation rather than a trivial placeholder. For a narrow privacy-gateway chat use case, the single-tool scope is reasonable.

    Completeness5/5

    The tool fully covers the server's apparent purpose: sending chat requests through the Lucairn gateway with provider routing and PII handling. There are no dead ends in the core workflow, and configuration concerns are handled through parameters and environment keys.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow