Skip to content

Add AegisGate MCP to ADDITIONAL.md frameworks list #5072

Closed as not planned
Closed as not planned

Description

@jcolvin1056

Request

Please add AegisGate MCP to the "For servers" frameworks list in ADDITIONAL.md.

About

AegisGate MCP is a security-first MCP server framework written in Go with 22 security layers:

  • Regex pattern matching (30 patterns) + ATLAS compliance scanning
  • CharCNN-BiLSTM neural ML threat detection (vendored ONNX runtime, no Python dependency)
  • Tool poisoning detection, RBAC, policy engine, audit logging, response scanning
  • Streamable HTTP transport with Mcp-Session-Id session management and SSE streaming
  • Zero external module dependencies (no require directives in go.mod)
  • Multi-arch (amd64/arm64), Cosign-signed releases, SBOM, 91% test coverage
  • Apache 2.0 licensed

Links

Suggested entry (alphabetical, under "For servers")

* **[AegisGate MCP](https://github.com/aegisgatesecurity/aegisgate-mcp)** (Go) - Security-first MCP server framework with 22 defense layers (regex, ATLAS compliance, CharCNN-BiLSTM neural ML detection, tool poisoning detection, RBAC, response scanning). Zero external dependencies. Streamable HTTP with Mcp-Session-Id. Apache 2.0. by **[AegisGate](https://github.com/aegisgatesecurity)**

This would go alphabetically before Anubis MCP in the existing list.

Why

AegisGate MCP is already published to the official MCP Registry and provides a unique security-focused framework option for the Go ecosystem. No other Go framework in the list offers built-in prompt injection detection, tool poisoning detection, or ML-based threat scanning.

Activity

  1. cliffhall commented on Oct 19, 2026

    @cliffhall
    Member

    Thank you for the suggestion. This repository holds only a small set of reference servers maintained by the MCP steering group, and it does not add new servers or list third-party ones. To make a server discoverable, publish it to the MCP Server Registry by following its quickstart guide; published servers can be browsed at registry.modelcontextprotocol.io.

    This is part of the backlog triage in #4875.

  2. added
    closed-out-of-scopeClosed: out of scope here; listings and new servers go to the MCP Registry (#4875)
    on Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    closed-out-of-scopeClosed: out of scope here; listings and new servers go to the MCP Registry (#4875)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions