Skip to main content
Glama
altirs

@altirs/mcp-server

by altirs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @altirs/mcp-server

No user-submitted related servers found.

    Related Servers

    • shipcheck-mcp

      noureldeensalama
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible AI agents to scan code for leaked secrets, copyleft licenses, unprotected routes, missing privacy policies, and risky card handling before committing or shipping.
      33 npm
      MIT
    • @guardbee/mcp-security-proxy by GuardBee

      @guardbee/mcp-security-proxyofficial

      GuardBee
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables transparent security for any MCP server by intercepting tool calls, blocking prompt injection attempts, masking PII in responses, and writing immutable audit logs.
      85 npm
      MIT

    • agentguard

      dockfixlabs
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables scanning of AI agent code for security vulnerabilities such as prompt injection, tool abuse, and data exfiltration, directly from MCP-compatible clients like Claude Code.
      2
      LGPL 3.0

    • mcp-gateway

      wxsh-hub
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables secure interoperability between LLM agents and MCP tool servers by sanitizing requests and responses, masking sensitive tokens, detecting PII, and performing server reputation scans.
      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

    A4.3/5.0

    Scored across 5 tools

    Disambiguation4/5

    check_content is a composite that overlaps with detect_pii, scan_injection, and check_safety, but its description clearly positions it as the default all-in-one gate, while the individual tools are for targeted use. check_hallucination is distinct because it requires source context.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (check_content, detect_pii, scan_injection, check_safety, check_hallucination). scan_injection deviates slightly from the check_* prefix used by the other three check tools, but the pattern is still readable and predictable.

    Tool Count5/5

    Five tools is a well-scoped set for a content-safety server. Each tool covers a distinct safety engine, with check_content serving as the umbrella entry point and the others providing focused checks.

    Completeness4/5

    The server covers the main guardrail categories: safety, PII, injection, and hallucination. A minor gap is the lack of a dedicated tool for updating or managing guardrail configurations, but the core detection surface is complete for its stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources