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 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

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. 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.

At the door

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

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.

Found and recommended

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

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 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 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 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.

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

All 360 checks, one company a day. Corrections to the corrections page.