Neon Zero-Trust MCP Gateway

io.github.AnsariiPublished by GitHub account Ansariiv1.0.0Updated Oct 24, 2026

AI security firewall & DLP proxy protecting API keys and blocking destructive commands.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

A remote MCP gateway that acts as a security firewall and DLP proxy, protecting API keys and blocking destructive commands for AI assistants.

What you can do
The manifest lists no tools, so capabilities come from the registry description only. It is positioned as an AI security firewall and data-loss-prevention proxy placed in front of assistant traffic. It is meant to protect API keys from exposure and to block destructive commands. No further tool-level detail is provided.
When to use it
Consider it when an assistant's traffic passes through external services and you want a proxy layer that guards API keys and screens out destructive commands. It is not useful if you need concrete tools rather than a protective gateway.
Requirements
A remote streamable HTTP endpoint; no local package, environment variables or headers are declared. The manifest declares no authentication, so check how access to the endpoint is controlled before relying on it.
Before you install
It sits in the path of assistant traffic and is described as a proxy, so consider what data passes through it and to the third-party host. The manifest declares no authentication; verify access control before use. No tool list is published, so its actual behavior cannot be confirmed from the listing.

Installation

In SourceWeft

  1. Open Neon Zero-Trust MCP Gateway in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Ansarii%2Fzero-trust-mcp-gateway/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "neon-zero-trust-gateway": {
      "type": "http",
      "url": "https://neon_innovation_lab--zero-trust-mcp-gateway.apify.actor/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.