Agent readiness · Managed databases
mongodb.com
10 of 16 measurable points under formula 9.2, measured on 2026-08-12. 15 checks exist; each is one HTTP request with a published rule, so every sentence below can be rerun and argued with.
A · Discovery
- PASSAnswers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
- PASSllms.txt publishedllms.txt present at https://www.mongodb.com/llms.txt and https://docs.mongodb.com/llms.txt, and the 12 links we sampled across the file all answer
- FAILDocs readable without JavaScriptOnly 66 characters render without JS
- PASSOn-demand agents not blockedNo on-demand agent is blocked
- N/APaths robots.txt points at answerrobots.txt names no concrete path, only patterns or nothing, so there is no claim to check
- PASSNo punishing crawl delayNo Crawl-delay applies to the agents we check
B · Agent entry
- FAILAgent entry pointNone of the 9 known agent entry paths returns a file rather than your page shell
- PASSOAuth dynamic client registrationregistration_endpoint published, and client_credentials is among the 11 advertised grants, so an unattended agent has a documented path to a token
- PASSMCP surfaceLive MCP endpoint at https://mcp.mongodb.com/mcp, answered 401 with an auth challenge
C · Registration
- PASSNo CAPTCHA in the signup HTMLNo CAPTCHA vendor in the server HTML. A widget mounted later by JavaScript would not show here.
- PASSSignup reachable without a browserForm renders in server HTML at https://www.mongodb.com/cloud/atlas/register
D · Provisioning
- FAILProgrammatic key provisioningNone of the 7 provisioning phrases appears in the 3 documents we read
- PASSFree tier or no-card trial stated in textFree tier or no-card signals at https://www.mongodb.com/pricing: "free tier", "Get started for free", "started for free"
E · Integration
- PASSTyped SDK on the registrymongodb@7.5.0 ships types, matched from the registry by who publishes it rather than by a link on your site
- FAILMachine-readable API descriptionNo OpenAPI spec at the 5 usual paths, none declared by https://www.mongodb.com/docs/, and no markdown negotiationPoint at your spec from your docs page with rel="service-desc" and an agent finds it without guessing.
Tell me when this changes
The failures here are the kind nobody notices. An edge rule that starts refusing agents changes nothing a person sees in a browser, so the first sign is usually an integration that quietly stopped working. We rescan weekly and write only when a verdict moves.
This page is the newest scan we hold for mongodb.com and changes when we rescan. It is not a judgement of the product: we measure whether an unattended run can get through, not whether the thing is any good. The whole corpus is published as JSON and CSV.