GitLab: the 360 agent-readiness check
GitLab scores 80 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. An authenticated MCP server behind a shield that stopped three of Ora's probes.
On 9 November 2026 the public site at gitlab.com scored 80 of 100 on Ora's agent-readiness scan, a B, in Ora's Developer Tools 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: GitLab offers strong discovery and developer access, but lacks WebMCP support for in-browser agent tool registration.
The score
| Layer | Asks | Points | Share |
|---|---|---|---|
| Usability | Can agents use it | 51 of 72 | 71% |
| Access | Can agents read it | 40 of 49 | 82% |
| Discovery | Can agents find and recommend it | 17 of 18 | 94% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade B | 80 of 100 | 80% |
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. 4 checks in this group do not apply to this site and are left out.
In the directory, GitLab 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 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.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| MCP server / manifest mcp-server | Partial | 5 of 6 | MCP server detected at https://support.gitlab.com/mcp; it requires authentication. Presence is verified (5/6), but Ora could not inspect its tools or verify access scopes without credentials. |
| MCP well-known discovery mcp-well-known-discovery | Pass | 2 of 2 | MCP server referenced in llms.txt |
| Public API with reachable endpoints public-api | Pass | 7 of 7 | REST API documentation found at https://docs.gitlab.com/ja-jp/. GraphQL endpoint at https://api.gitlab.com/graphql is reachable; introspection requires authentication (API key / OAuth), |
| Public API/docs linked from homepage public-api-docs | Pass | 3 of 3 | Documentation site found at https://docs.gitlab.com |
| Developer portal developer-portal | Pass | 6 of 6 | Developer portal found at /developers |
| API catalog (RFC 9727) api-catalog-rfc9727 | Fail | 0 of 2 | No /.well-known/api-catalog found (RFC 9727) |
| OAuth 2.0 support oauth-support | Pass | 5 of 5 | OAuth authorization server metadata at https://support.gitlab.com/mcp/oauth |
| OAuth Protected Resource metadata (RFC 9728) oauth-protected-resource | Pass | 2 of 2 | no detail published |
| auth.md exists auth-md-exists | Fail | 0 of 2 | No /auth.md found at site root |
| WebMCP support webmcp | Fail | 0 of 5 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 1 of 1 same-origin script bundle(s) for modelContext registrations) |
| 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: @gitlab/orbit |
| Multi-language SDK packages rest-sdk-packages | Partial | 2 of 3 | SDK packages found in npm, rubygems |
| Rate limit response headers rate-limit-headers | Pass | 2 of 2 | no detail published |
| Idempotency-Key support idempotency-key-support | Fail | 0 of 3 | GraphQL introspection auth-gated and no idempotency documentation found on GraphQL-tagged pages |
At the door
What the site answers when a request arrives with an agent's user agent, and what robots.txt says to agents. One check in this group does not apply to this site and is left out.
| 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://gitlab.com/. Declared policy only; |
| Content behind auth docs-auth-gate | Pass | 2 of 2 | All 5 sampled pages are publicly readable (1 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 |
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. 2 checks in this group do not apply to this site and are left out.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Content without JavaScript content-no-js | Partial | 1 of 3 | Homepage: 5008 chars, semantic headings (1 H1 + 7 H2s + 16 H3s), 8.4% content ratio. Sampled pages with almost no text without JavaScript (4 of 5): https://gitlab.com/explore/groups (156 chars), |
| Page token budget page-token-budget | Pass | 1 of 1 | All 6 measured pages fit an agent context budget (largest ~1K tokens) |
| Sitemap exists sitemap | Pass | 2 of 2 | Valid sitemap found at /sitemap.xml with 19358 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://docs.gitlab.com/llms.txt. |
| llms.txt formatting llms-txt-formatting | Partial | 1 of 2 | The llms.txt is well-formatted with markdown links, but at 87,620 characters it exceeds the 30,000-character recommendation for a navigation index. |
| llms.txt links resolve llms-txt-links-resolve | Pass | 2 of 2 | no detail published |
| Markdown agent docs markdown-negotiation | Fail | 0 of 1 | Missing markdown content negotiation. Homepage returned text/plain when probed with Accept: text/markdown (expected text/markdown), and none of the well-known root paths (/llms.md, /auth.md, /agents.md, /developers.md, |
| 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 | No agent mode view detected at ?mode=agent (optional) |
| JSON-LD structured data json-ld | Partial | 3 of 4 | JSON-LD Organization found - missing description and one of sameAs / logo / address / contactPoint on this entity |
| Organization schema completeness org-schema-completeness | Partial | 1 of 2 | Organization schema found but missing: contactPoint, 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-US", og:image, og:type |
Found and recommended
Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read. One check in this group does not apply to this site and is left out.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Brand name discoverability brand-search-accuracy | Pass | 3 of 3 | gitlab.com ranks #2 for "GitLab DevSecOps" and #5 for "GitLab DevOps" |
| Wikipedia / Wikidata entity presence wikipedia-presence | Pass | 4 of 4 | Wikipedia "GitLab" and Wikidata Q16639197 both verified - domain confirmed on both sources |
| 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 | Pass | 2 of 2 | no detail published |
| Listed on skills.sh skills-sh-listed | Fail | 0 of 1 | No official skills self-published on skills.sh (100 community skills with potential relation to this domain found, but only self-published official skills count) |
| ARD discovery ard-catalog | Fail | 0 of 1 | No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json |
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 gitlab.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 GitLab, 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.
- WebMCP support: fail, 0 of 5, about 3.1 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 1 of 1 same-origin script bundle(s) for modelContext registrations)
- GraphQL typed error model: fail, 0 of 3, about 1.9 points to gain. Ora saw: GraphQL introspection auth-gated and no typed graphql error model documentation found on GraphQL-tagged pages
- Idempotency-Key support: fail, 0 of 3, about 1.9 points to gain. Ora saw: GraphQL introspection auth-gated and no idempotency documentation found on GraphQL-tagged pages
- Content without JavaScript: partial, 1 of 3, about 1.4 points to gain. Ora saw: Homepage: 5008 chars, semantic headings (1 H1 + 7 H2s + 16 H3s), 8.4% content ratio. Sampled pages with almost no text without JavaScript (4 of 5): https://gitlab.com/explore/groups (156 chars),
- Pricing info accessible: partial, 1 of 3, about 1.4 points to gain. Ora saw: Pricing link found but no dedicated pricing page at standard path
Our read
GitLab's B is a read with a shield in the middle of it. The MCP server at support.gitlab.com/mcp answers and requires authentication, with OAuth metadata beside it at /mcp/oauth, and llms.txt references the server; the CLI check is met by @gitlab/orbit on npm and SDKs are in npm and rubygems. Three act-layer probes were answered 403 by a bot shield rather than by the site, the OpenAPI specification at /swagger.json, the A2A agent card and the agent skills index, so those rows are unverified and fall out of the maximum rather than counting against it, which is part of why the Access layer reads 40 of 49. The reading side is the strongest of the developer platforms so far: a home page with one H1, seven H2s and sixteen H3s at an 8.4 percent text ratio, five readable sampled pages and an open door. The shield is the thing to fix first, because it hides whatever else is 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 70All 360 checks, one company a day. Corrections to the corrections page.