MongoDB: the 360 agent-readiness check

MongoDB scores 78 of 100 on Ora's agent-readiness scan, a B, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 3: a public API, OAuth, a command line. Two agent files published and neither parses as JSON.

On 9 November 2026 the public site at mongodb.com scored 78 of 100 on Ora's agent-readiness scan, a B, in Ora's Infrastructure category. 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: MongoDB offers strong access and usability foundations and passes most discovery checks, but it lacks a published OpenAPI specification for agents.

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. 2 checks in this group do not apply to this site and are left out.

In the directory, MongoDB no MCP endpoint on record; the connector run of 4 November 2026 is on the entry page. Ora's MCP server check for the same domain reads partial; 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 mongodb.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 MongoDB, 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.

• OpenAPI spec published: fail, 0 of 7, about 3.8 points to gain. Ora saw: No OpenAPI/Swagger specification found
• Scoped permissions: fail, 0 of 5, about 3.2 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found
• WebMCP support: fail, 0 of 5, about 3.2 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 12 of 12 same-origin script bundle(s) for modelContext registrations)
• Brand name discoverability: partial, 1 of 3, about 2.5 points to gain. Ora saw: mongodb.com ranks #8 for "MongoDB" (searched your brand name alone: no main product term from your homepage qualified)
• Function calling compatibility: fail, 0 of 2, about 1.3 points to gain. Ora saw: Poor compatibility: missing operationIds (0/0) and parameter schemas

Our read

MongoDB has two agent files that do not parse, which is a rarer failure than having none. The A2A agent card at /.well-known/agent-card.json exists and contains invalid JSON, and the agent skills index at /.well-known/agent-skills/index.json exists and is not valid JSON either, so both score as absent after someone did the work of publishing them. The rest of the act layer is in order: an MCP server at mcp.mongodb.com that requires authentication, OAuth authorization server metadata at authorize.mongodb.com, REST documentation scoring 7 of 7, SDKs in npm and rubygems, and an llms.txt on the main domain. The missing OpenAPI specification is the largest single gap at about 4 points, and the specification that would fix it would also fix the function-calling check, which found no operationIds. A JSON validator in the build is the whole first fix.

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.