Skip to main content
Glama
12211725-star

Hospital WAF MCP

by 12211725-star
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Related Servers

Alternatives to Hospital WAF MCP

No user-submitted related servers found.

    Related Servers

    • YaraFlux MCP Server

      ThreatFlux
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that enables AI assistants to perform YARA rule-based threat analysis on files and URLs, supporting comprehensive rule management and detailed scanning results.
      23
      MIT

    • Clinical MCP Server

      dianapopovici
      A
      license
      Not graded
      quality
      D
      maintenance
      A governed, audited Model Context Protocol server that provides AI agents with secure, read-only access to a clinical knowledge base through least-privilege tools, policy validation, and append-only audit logging.
      MIT

    • PromptShield MCP

      Zero-Harm-AI
      A
      license
      B
      quality
      A
      maintenance
      A Model Context Protocol server that lets AI agents and runtime firewalls call PromptShield-style safety checks for text, chat messages, prompts, tool inputs, and generated outputs.
      4
      1
      MIT

    • guardrails-mcp-server

      ExpertVagabond
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for AI agent security guardrails. Provides input validation, prompt injection detection, PII redaction, output filtering, policy enforcement, rate limiting, and comprehensive audit logging.
      31 npm
      1
      MIT

    • Smart EHR MCP Server

      jmandel
      A
      license
      Not graded
      quality
      F
      maintenance
      A Model Context Protocol server that connects AI tools to Electronic Health Records using SMART on FHIR, allowing secure searching, querying, and analysis of patient data from compatible EHRs.
      87
      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/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: checking requests, reloading rules, viewing statistics, and running self-tests. No two tools overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent 'waf_verb_noun' pattern using snake_case, with clear and descriptive verbs (check, reload, rule_stats, run_self_tests).

    Tool Count5/5

    With 4 tools, the set is well-scoped for a WAF server, covering essential operations without being unnecessarily large or too minimal.

    Completeness4/5

    The tools cover the main use cases (request checking, rule management, statistics, testing). Minor gaps exist, such as no tool for individually viewing or modifying specific rules, but core workflows are supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources