Agent MCP Directory

Neon: MCP server, CLI and agent surfaces

Sign-in required, tools not seen, not counted. The MCP endpoint listed for Neon at mcp.neon.tech answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in.

Fact sheet

CompanyNeon
Domainneon.com
CategoryInfrastructure (Ora leaderboard category)
MCP serverSign-in required (OAuth with client registration)
Ora score88, grade A; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for neon.com, a vendor-published score)
Company found throughthe vendor's own documentation; the official MCP Registry
Last verified4 November 2026

MCP server

Endpointhttps://mcp.neon.tech/mcp
How it was foundlisted in the vendor's own documentation; the official MCP Registry
Transportstreamable-http
HTTP status401
Connected4 November 2026, 20:03 UTC
Handshake time1,055 ms over 1 attempt
Documentationneon.com

The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools.

Connector log

2 connections on 4 November 2026, read-only methods only

  • 19:58:30Z https://mcp.neon.tech/mcp sent initialize result auth-required (HTTP 401) 914 ms
  • 20:03:44Z https://mcp.neon.tech/mcp sent initialize result auth-required (HTTP 401) 1055 ms

Authentication

Auth typeOAuth with client registration
What the challenge saidBearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://mcp.neon.tech/.well-known/oauth-protected-resource/mcp"
Protected resource metadatamcp.neon.tech
Authorization server metadatamcp.neon.tech
Registration endpointhttps://mcp.neon.tech/api/register
Client ID metadata documentssupported

The sign-in route, step by step

  1. Request https://mcp.neon.tech/mcp without a token. It answers 401 and a WWW-Authenticate header.
  2. Read the protected resource metadata at https://mcp.neon.tech/.well-known/oauth-protected-resource/mcp to find the authorization server.
  3. Register a client at the registration endpoint https://mcp.neon.tech/api/register (dynamic client registration), so no human has to create an app first.
  4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes.

See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.

CLI

Packageneonctl on npm (page)
Existsyes
Latest version8.18.0
Last publish3 November 2026
Command namesneon, neonctl
Checked4 November 2026

Other agent surfaces

Agent surfaces other than MCP and CLI
SurfaceResult
OpenAPI fileFound: neon.com (JSON, via a direct request).
WebMCP in the initial HTMLNot detected on the home page by the shared crawl.
MCP discovery fileNot found (the crawl got a non-200 answer).
A2A agent cardNot found (the crawl got a non-200 answer).
A2A agent card (older path)Not found (the crawl got a non-200 answer).
agents.jsonNot found (the crawl got a non-200 answer).
OAuth authorization server metadataNot found (the crawl got a non-200 answer).
NLWeb endpointNot checked in this edition.

Registry listings

Registry listings
RegistryListed
Official MCP RegistryYes: com.neon/mcp
GitHub MCP RegistryNo
awesome-remote-mcp-serversNo
SmitheryNot checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
GlamaNot checked: Glama's API needs a key and attribution terms.