Skip to main content
Glama
hhhashexe

ShieldNet MCP

by hhhashexe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to ShieldNet MCP

No user-submitted related servers found.

    Related Servers

    • suprawall

      wiserautomation
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables deterministic zero-trust security for AI agents, providing prompt injection protection, PII scrubbing, and policy enforcement before agentic actions reach production systems.
      2
      Apache 2.0

    • agent-chokepoint

      ydarwish1
      A
      license
      Not graded
      quality
      B
      maintenance
      A security checkpoint for AI agents that intercepts and polices tool calls with allow/block/ask verdicts, taint tracking, and audit logging.
      Apache 2.0

    • ZugaShield

      Zuga-Technologies
      A
      license
      Not graded
      quality
      A
      maintenance
      A 7-layer security system for AI agents that detects and blocks prompt injection, data exfiltration, and malicious tool calls. It enables real-time scanning of inputs, outputs, and tool definitions to protect agentic workflows from emerging AI-specific threats.
      1
      MIT

    • intaris

      fpytloun
      F
      license
      Not graded
      quality
      A
      maintenance
      Guardrails service for AI agents that evaluates every tool call for safety and alignment before execution, providing default-deny policy, LLM safety evaluation, and audit trail.
      76 PyPI
      22
      -
    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.7/5.0

    Scored across 6 tools

    Disambiguation3/5

    scan_url and assess_risk both scan a URL and could be confused, though assess_risk explicitly returns a governance decision. check_headers overlaps heavily with the headers module inside scan_url, creating ambiguity about which tool to call. Descriptions help clarify intent, but some boundaries remain fuzzy.

    Naming Consistency4/5

    Most tools follow a clear verb_noun snake_case pattern: scan_url, check_headers, scan_history, compare_scans, assess_risk. governance_policy deviates by using a noun_noun name rather than a verb-led action name like view_policy, but the overall naming style is still predictable.

    Tool Count5/5

    Six tools is a well-scoped set for a security scanning and governance server. Each tool has a distinct role within the workflow, and the count is neither bloated nor too thin.

    Completeness4/5

    The tool surface covers scanning, risk assessment, governance policy, history, and comparison, which are the core needs for this domain. A minor gap is that users cannot retrieve detailed findings from a past scan, only grades and scores, but agents can work around this by re-scanning.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources