---
title: "Neon: the 360 agent-readiness check | Agent MCP Directory"
description: "Neon on Ora's agent-readiness scan, read 2026-11-09: 88 of 100, grade A, with the MCP, API and OAuth surfaces an agent can call."
canonical: https://agentmcpdirectory.com/blog/neon-agent-readiness
site: "Agent MCP Directory"
last_updated: 2026-11-09
date: 2026-11-09
section: "360 checks"
---

# Neon: the 360 agent-readiness check | Agent MCP Directory

> Neon on Ora's agent-readiness scan, read 2026-11-09: 88 of 100, grade A, with the MCP, API and OAuth surfaces an agent can call.

Source: https://agentmcpdirectory.com/blog/neon-agent-readiness
Site: Agent MCP Directory
Last reviewed: 2026-11-09

# Neon: the 360 agent-readiness check

Neon scores 88 of 100 on Ora's agent-readiness scan, an A, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 4: an MCP server, an OpenAPI specification, a public API, a command line. A live handshake and a server card in the AI catalog, with OAuth only described.

On 9 November 2026 the public site at neon.com scored 88 of 100 on [Ora's](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check) agent-readiness scan, an A. Ora probes a site the way an agent would: it requests pages with the agents' own user agents, reads robots.txt, looks for the files agents read, and tries the API, MCP and payment surfaces. This check reads the act layer first, because that is what the directory records, then the door, what an agent can read, and whether the company is found and recommended. Ora's one-line summary: Neon provides comprehensive Postgres API access and discovery, but lacks JSON error responses in its REST endpoints.

## The score

| Layer | Asks | Points | Share |
| --- | --- | --- | --- |
| Usability | Can agents use it | 81 of 96 | 84% |
| Access | Can agents read it | 61 of 65 | 94% |
| Discovery | Can agents find and recommend it | 13 of 15 | 87% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade A | 88 of 100 | 88% |

## What an agent can do

The surfaces an agent acts on: an API it can find and call, an MCP server, an agent card, OAuth metadata, a command line. This is the layer the directory records, so it comes first.

In the directory, Neon sign-in required, tools not seen, not counted; the connector run of 4 November 2026 is on [the entry page](https://agentmcpdirectory.com/directory/neon-com/). Ora's MCP server check for the same domain reads pass; the two look for different things, the directory for a server that answers a handshake and lists tools, Ora for a server it can find from the site.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| MCP server / manifest mcp-server | Pass | 6 of 6 | MCP server connected via Streamable HTTP - mcp-server-neon v1.0.0 (protocol 2025-11-25) |
| MCP well-known discovery mcp-well-known-discovery | Pass | 2 of 2 | MCP server card listed in /.well-known/ai-catalog.json |
| Public API with reachable endpoints public-api | Pass | 7 of 7 | Documented REST API detected; endpoints require authentication (API key / OAuth), which is expected for agent access. Best-of-protocols score: 7/7. |
| Public API/docs linked from homepage public-api-docs | Pass | 3 of 3 | API/docs link found on homepage and resolves: /docs |
| Developer portal developer-portal | Pass | 6 of 6 | Developer portal found at /docs |
| OpenAPI spec published openapi-spec | Pass | 7 of 7 | OpenAPI spec found at https://neon.com/api_spec/release/v2.json (version: 3.0.3) |
| API catalog (RFC 9727) api-catalog-rfc9727 | Pass | 2 of 2 | no detail published |
| A2A / agent-card a2a-agent-card | Fail | 0 of 2 | No A2A agent card found at /.well-known/agent-card.json |
| Agent discovery file agent-discovery-file | Pass | 2 of 2 | Agent Skills index (agentskills.io) found at /.well-known/agent-skills/index.json with 10 skill(s) |
| OAuth 2.0 support oauth-support | Partial | 3 of 5 | OAuth mentioned in documentation at https://neon.com/auth.md but no OAuth or OpenID Connect endpoint responded |
| OAuth Protected Resource metadata (RFC 9728) oauth-protected-resource | Fail | 0 of 2 | No /.well-known/oauth-protected-resource found (RFC 9728) |
| auth.md exists auth-md-exists | Pass | 2 of 2 | no detail published |
| WebMCP support webmcp | Pass | 5 of 5 | Imperative WebMCP API detected (document.modelContext.registerTool in script bundle /_next/static/immutable/chunks/2vl9he_7n76_5.js). |
| NLWeb /ask endpoint nlweb-ask | Fail | 0 of 1 | No NLWeb-conformant /ask endpoint found via GET or POST |
| CLI tool available cli-tool | Pass | 3 of 3 | CLI package found on npm: neon |
| Multi-language SDK packages rest-sdk-packages | Partial | 2 of 3 | SDK packages found in npm, pypi |
| Rate limit response headers rate-limit-headers | Fail | 0 of 2 | No REST rate-limit headers found on probed endpoints |
| Idempotency-Key support idempotency-key-support | Fail | 0 of 3 | No REST Idempotency-Key support detected |
| JSON error responses json-error-responses | Pass | 4 of 4 | no detail published |

## At the door

What the site answers when a request arrives with an agent's user agent, and what robots.txt says to agents.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Not blocked by bot detection bot-detection | Pass | 2 of 2 | Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot). |
| Agent crawler reachability agent-crawler-reachability | Pass | 2 of 2 | Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable |
| robots.txt AI crawler policy robots-ai-policy-quality | Pass | 2 of 2 | AI search crawlers: allowed in 18 of 18 checks (3 crawlers on 6 pages). AI training crawlers: allowed in 12 of 12 checks (2 crawlers on 6 pages), not scored. |
| robots.txt agent-user policy robots-agent-user-policy | Pass | 2 of 2 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://neon.com/. Declared policy only; |
| Content behind auth docs-auth-gate | Pass | 2 of 2 | All 5 sampled pages are publicly readable (5 with substantive content) |
| Homepage not hidden from search noindex-directives | Pass | 1 of 1 | No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search. |
| Redirect hygiene redirect-hygiene | Pass | 1 of 1 | no detail published |
| Web Bot Auth directory web-bot-auth-directory | Fail | 0 of 2 | No /.well-known/http-message-signatures-directory found |

## What an agent can read

Whether the text is in the first response, what the site publishes for agents, and how it describes itself to them.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Content without JavaScript content-no-js | Partial | 2 of 3 | 3369 chars with H1, but 1.6% content ratio is below the 5% target |
| Page token budget page-token-budget | Pass | 1 of 1 | All 8 measured pages fit an agent context budget (largest ~2K tokens) |
| Sitemap exists sitemap | Pass | 2 of 2 | Valid sitemap found at https://neon.com/sitemap.xml with multiple sitemaps entries |
| Sitemap freshness (lastmod) sitemap-lastmod | Pass | 1 of 1 | no detail published |
| llms.txt exists llms-txt-exists | Pass | 1 of 1 | Found the llms.txt at https://neon.com/llms.txt. |
| llms.txt formatting llms-txt-formatting | Pass | 2 of 2 | The llms.txt is well-formatted: 250 lines with markdown links, 28,872 characters in total. |
| llms.txt links resolve llms-txt-links-resolve | Pass | 2 of 2 | no detail published |
| Markdown agent docs markdown-negotiation | Pass | 1 of 1 | Path-suffix markdown docs served with text/markdown content-type: /auth.md, /index.md |
| Markdown URL fallback markdown-url-fallback | Pass | 2 of 2 | no detail published |
| Bot-UA markdown serving agent-ua-markdown | Fail | 0 of 1 | No probed bot User-Agent (ChatGPT-User, Claude-User, Perplexity-User) receives markdown when requesting HTML. Optional: detect AI-bot UAs server-side and serve them a markdown representation directly. |
| Agent mode view agent-mode-view | Fail | 0 of 2 | ?mode=agent returns same content as homepage (no dedicated agent view) |
| JSON-LD structured data json-ld | Pass | 4 of 4 | Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (1 block(s)) |
| Organization schema completeness org-schema-completeness | Partial | 1 of 2 | Organization schema found but missing: address |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Pass | 2 of 2 | no detail published |
| Schema type breadth schema-type-breadth | Fail | 0 of 2 | No extended schema types found - AI can only answer basic questions about this entity |
| Metadata completeness metadata-completeness | Pass | 2 of 2 | All metadata signals present: canonical URL, lang="en", og:image, og:type |
| Agent instruction / when-to-use agent-instruction | Pass | 3 of 3 | no detail published |

## Found and recommended

Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Brand name discoverability brand-search-accuracy | Partial | 1 of 3 | neon.com ranks #8 for "Neon serverless database" |
| Wikipedia / Wikidata entity presence wikipedia-presence | Fail | 0 of 4 | No Wikipedia article or Wikidata entity found for "neon" - creating a Wikipedia page and a Wikidata item with P856 = neon.com is the highest-impact step for AI search citation coverage |
| Developer resource discoverability agentic-search-specific | Pass | 3 of 3 | no detail published |
| Listed in MCP registries mcp-registry-listed | Pass | 1 of 1 | no detail published |
| NPM/PyPI SDK package npm-sdk-package | Pass | 1 of 1 | no detail published |
| ChatGPT app listed chatgpt-app-listed | Fail | 0 of 2 | Not found in ChatGPT app directory |
| Registry branding registry-branding | Pass | 2 of 2 | no detail published |
| Listed on skills.sh skills-sh-listed | Pass | 1 of 1 | no detail published |
| ARD discovery ard-catalog | Pass | 1 of 1 | no detail published |

## Payments

The agent payment protocols Ora probes for. A site that sells nothing has nothing here, and Ora scores the layer out of zero when none applies. None of the 6 payment checks applied to neon.com.

## The fixes worth most points

Ora attaches an estimate to each failing or partial check: how many points the site would gain by passing it. These are the 5 with the largest estimates for Neon, with what Ora observed. The wording of each fix is Ora's; [the 28 checks it runs on an MCP server](https://agentmcpdirectory.com/mcp-checks/) are listed with their layer and tier.

-   Brand name discoverability: partial, 1 of 3, about 3 points to gain. Ora saw: neon.com ranks #8 for "Neon serverless database"
-   Idempotency-Key support: fail, 0 of 3, about 1.4 points to gain. Ora saw: No REST Idempotency-Key support detected
-   Scoped permissions: partial, 2 of 5, about 1.4 points to gain. Ora saw: OpenAPI declares security schemes but no named OAuth scopes - agents get all-or-nothing access. Declare per-scope grants (e.g. read:\*, write:\*) in the spec.
-   Schema type breadth: fail, 0 of 2, about 1 points to gain. Ora saw: No extended schema types found - AI can only answer basic questions about this entity
-   OAuth 2.0 support: partial, 3 of 5, about 0.9 points to gain. Ora saw: OAuth mentioned in documentation at https://neon.com/auth.md but no OAuth or OpenID Connect endpoint responded

## Our read

Neon is one of the few companies in this directory whose MCP server completed a live handshake with Ora: mcp-server-neon version 1.0.0 over Streamable HTTP on protocol 2025-11-25, with the server card listed in /.well-known/ai-catalog.json, which is the discovery route the checklist asks for. Around it sit an OpenAPI 3.0.3 specification at neon.com/api\_spec/release/v2.json, the neon CLI on npm, SDKs in npm and PyPI, an agent skills index with ten skills, an llms.txt, markdown twins served as text/markdown and a WebMCP tool registered in a script bundle. The 88 is held back by small things: OAuth is described in auth.md but no OAuth or OpenID Connect endpoint answered, the specification names security schemes without scopes, REST has no Idempotency-Key, and the brand search places neon.com eighth. The home page is 1.6 percent text. Ora reads it without a category; the checklist reads it as the handshake done right.

## Test your own surfaces

The scan above is free and needs no account: enter a domain at [ora.ai](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check) and read the same four layers for your own site. For an MCP server, Ora scans the server URL itself and runs 28 of its 132 public checks on it, which is why it is the check this directory recommends; [the reasons, the limits and the alternatives](https://agentmcpdirectory.com/test-your-mcp-server/) are on their own page. The command below runs the same audit from a terminal and exits with 1 under the score you set, so it can gate a deploy.

```bash
npx ax@0.10 audit https://example.com --min-score 70
```

[All 360 checks](https://agentmcpdirectory.com/blog/), one company a day. Corrections to [the corrections page](https://agentmcpdirectory.com/corrections/).

Edition

4 November 2026

Method

[How rows are verified](https://agentmcpdirectory.com/method/)

Data

[CSV and JSON](https://agentmcpdirectory.com/data/)

Markdown

[This page as markdown](https://agentmcpdirectory.com/blog/neon-agent-readiness/index.md)

## Sources

-   [Ora's scan of neon.com, GET /api/score (vendor)](https://ora.ai/api/score/neon.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check), read 9 November 2026
-   [Ora check catalogue, contract 1.38.0](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check), read 5 November 2026
-   [neon.com, the company's site](https://neon.com/), read 9 November 2026

Last reviewed 9 November 2026