A local security proxy MCP server for Neon's serverless Postgres API — default-deny, policy-enforced AI branch access.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"neon-guard-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# neon-guard-mcp 🛡️ Neon's official MCP server is amazing, but giving an LLM full admin access to your infrastructure is terrifying. **neon-guard-mcp** acts as a local security proxy, giving your AI agent the exact tools it needs to branch and test code, while completely air-gapping your production data and master keys. --- ## Features - **Default-deny whitelist** — only a small set of branch-scoped tools are exposed; there is no tool for deleting projects, managing users, modifying production, or accessing connection strings for branches the proxy did not create. - **Provenance gating** — authorization to retrieve a connection string, delete, or reset a branch requires that the proxy itself created it (tracked in `.neon-guard-state.json`). A matching name prefix alone is not sufficient. - **Schema-only branches by default** — new branches are created with `init_source: schema-only`, so no production rows are ever copied into an agent-accessible branch. - **Short-lived branches** — configurable expiry (default 24 h); Neon deletes the branch automatically, invalidating the embedded credential. - **Project allowlist** — the proxy refuses to act on any project not explicitly listed in your config, even if the API key has broader access. - **NEON_API_KEY never leaves the proxy process** — the LLM receives only tool results, never the key itself. - **Configurable tool disabling** — remove individual tools from the schema if your threat model requires it. --- ## Architecture ``` Claude Code (or any MCP client) | | stdio (JSON-RPC) v +---------------------------+ | neon-guard-mcp proxy | | - holds NEON_API_KEY | | - enforces policy | | - tracks provenance | | - rewrites / filters | +---------------------------+ | | HTTPS (Neon REST API v2) v console.neon.tech ``` The LLM calls tools. The proxy validates every call against config and provenance state, then translates allowed calls in…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.