Skip to main content
Glama
gsepcore

GSEP-MCP

Official
by gsepcore
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to GSEP-MCP

No user-submitted related servers found.

    Related Servers

    • Shrike Security MCP Server

      Shrike-Security
      A
      license
      A
      quality
      B
      maintenance
      Protects AI agents from threats like prompt injection, jailbreaks, and SQL injection through a multi-layer scanning pipeline. It also enables PII redaction and rehydration to ensure data privacy during LLM interactions.
      12
      108 npm
      2
      Apache 2.0

    • AgentSoap MCP Server

      bp46
      A
      license
      Not graded
      quality
      C
      maintenance
      A security interceptor for AI agents that mitigates prompt injections and data loss in autonomous workflows.
      365 npm
      1
      MIT

    • Prompt Rejector MCP

      revsmoke
      A
      license
      Not graded
      quality
      A
      maintenance
      Protects AI agents from prompt injection attacks, jailbreak attempts, and common web vulnerabilities by screening untrusted input through semantic LLM analysis and static pattern matching.
      101 npm
      2
      ISC

    • Carapace MCP Server

      jdesl55
      A
      license
      Not graded
      quality
      D
      maintenance
      A local-first security system for autonomous AI agents that provides tools for security verification, goal anchoring, and action logging. It protects against prompt injection and goal drift by enforcing user-defined rules and offering performance insights through session grading.
      9 npm
      MIT

    • 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
    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 10 tools

    Disambiguation5/5

    Each tool has a distinct role in the security pipeline: scanning input, output, actions; middleware hooks; chat; status; and feedback. No two tools serve the same purpose; even similar-sounding tools like gsep_scan_input and gsep_before_llm are clearly differentiated by their descriptions.

    Naming Consistency5/5

    All tools follow the 'gsep_' prefix with a verb_noun pattern (e.g., scan_input, get_status, record_feedback) or preposition_noun (before_llm, after_tool). The naming is consistent, descriptive, and predictable.

    Tool Count5/5

    With 10 tools, the server is well-scoped for its domain of LLM security pipeline. Each tool addresses a specific step or integration point, neither too few nor too many.

    Completeness5/5

    The tool set covers the complete lifecycle: input scanning, action scanning, output scanning, middleware hooks for external agents, chat pipeline, status monitoring, and feedback. There are no obvious gaps for the intended purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources