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

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

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

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

# Zoom: the 360 agent-readiness check

Zoom scores 66 of 100 on Ora's agent-readiness scan, a C, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 2: a public API, OAuth. Sixty-four skills published, and no server where an agent could call them.

On 9 November 2026 the public site at zoom.us scored 66 of 100 on [Ora's](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check) agent-readiness scan, a C, in Ora's Communication & Support 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: Zoom offers solid discoverability and SDK packages, but lacks a published OpenAPI specification for agents to call its API.

## The score

| Layer | Asks | Points | Share |
| --- | --- | --- | --- |
| Usability | Can agents use it | 34 of 76 | 45% |
| Access | Can agents read it | 43 of 56 | 77% |
| Discovery | Can agents find and recommend it | 14 of 15 | 93% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade C | 66 of 100 | 66% |

## 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, Zoom sign-in required, tools not seen, not counted; the connector run of 4 November 2026 is on [the entry page](https://agentmcpdirectory.com/directory/zoom-us/). Ora's MCP server check for the same domain reads fail; 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 | Fail | 0 of 6 | No MCP server or manifest found |
| MCP well-known discovery mcp-well-known-discovery | Fail | 0 of 2 | No MCP server URL discovered |
| Public API with reachable endpoints public-api | Pass | 7 of 7 | API described in documentation at https://docs.zoom.us but no machine-verifiable API surface confirmed. GraphQL endpoint at https://api.zoom.us/v1/graphql is reachable; |
| Public API/docs linked from homepage public-api-docs | Pass | 3 of 3 | Documentation site found at https://docs.zoom.us |
| Developer portal developer-portal | Pass | 6 of 6 | Developer portal found at /developer |
| OpenAPI spec published openapi-spec | Fail | 0 of 7 | No OpenAPI/Swagger specification found |
| API catalog (RFC 9727) api-catalog-rfc9727 | Partial | 1 of 2 | api-catalog linkset[0] has no 'item' entries |
| 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 64 skill(s) |
| OAuth 2.0 support oauth-support | Pass | 5 of 5 | OpenID Connect discovery endpoint found at https://zoom.us |
| 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 | 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 |
| NLWeb /ask endpoint nlweb-ask | Fail | 0 of 1 | No NLWeb-conformant /ask endpoint found via GET or POST |
| CLI tool available cli-tool | Fail | 0 of 3 | No CLI tool found |
| Multi-language SDK packages rest-sdk-packages | Partial | 1 of 3 | SDK package found only in npm |
| Rate limit response headers rate-limit-headers | Fail | 0 of 2 | GraphQL introspection auth-gated and no header convention documented on GraphQL-tagged pages |
| Idempotency-Key support idempotency-key-support | Fail | 0 of 3 | GraphQL introspection auth-gated and no idempotency documentation found on GraphQL-tagged pages |
| 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 12 of 12 checks (3 crawlers on 4 pages). AI training crawlers: allowed in 8 of 8 checks (2 crawlers on 4 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://zoom.us/. 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. 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 | Pass | 3 of 3 | Homepage: 8293 chars, semantic headings (1 H1 + 6 H2s + 13 H3s), 6.7% content ratio. 5 of 5 sampled inner pages have text without JavaScript. |
| Page token budget page-token-budget | Pass | 1 of 1 | All 6 measured pages fit an agent context budget (largest ~6K tokens) |
| Sitemap exists sitemap | Pass | 2 of 2 | Valid sitemap found at https://zoom.us/sitemap.xml with 5454 entries |
| Sitemap freshness (lastmod) sitemap-lastmod | Fail | 0 of 1 | None of the 500 sampled sitemap entries carries a lastmod date. Add <lastmod> (W3C datetime) so agents can prioritize fresh content. |
| llms.txt exists llms-txt-exists | Partial | 0 of 1 | A file is present at https://docs.zoom.us/.well-known/llms.txt, but it returns an HTML page rather than a plain-text llms.txt. |
| llms.txt formatting llms-txt-formatting | Fail | 0 of 2 | No llms.txt found to evaluate quality |
| Markdown agent docs markdown-negotiation | Fail | 0 of 1 | Missing markdown content negotiation. Homepage returned text/html 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, |
| Markdown URL fallback markdown-url-fallback | Fail | 0 of 2 | Homepage does not support the .md suffix. Probed https://zoom.us/index.md and it did not return markdown (expected text/markdown content-type or a heading-led non-HTML body). |
| 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 | Partial | 3 of 4 | JSON-LD Person found - missing description, url, and one of sameAs / jobTitle / worksFor on this entity |
| 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. 2 checks in this group do not apply to this site and are left out.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Brand name discoverability brand-search-accuracy | Pass | 3 of 3 | zoom.us ranks #5 for "Zoom UCaaS" but is not in the top 10 for "Zoom Unified Communications" |
| Wikipedia / Wikidata entity presence wikipedia-presence | Partial | 2 of 4 | Wikipedia "Zoom (software)" verified - create a Wikidata item with P856 (official website) = zoom.us to complete knowledge graph coverage |
| Developer resource discoverability agentic-search-specific | Pass | 3 of 3 | 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 | Pass | 1 of 1 | no detail published |
| 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 zoom.us.

## 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 Zoom, 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.

-   OpenAPI spec published: fail, 0 of 7, about 4.2 points to gain. Ora saw: No OpenAPI/Swagger specification found
-   MCP server / manifest: fail, 0 of 6, about 3.5 points to gain. Ora saw: No MCP server or manifest found
-   Scoped permissions: fail, 0 of 5, about 2.9 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found
-   WebMCP support: fail, 0 of 5, about 2.9 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found
-   MCP Apps support: fail, 0 of 4, about 2.3 points to gain. Ora saw: No MCP Apps support detected - this product has an in-agent UI surface but exposes no ui:// resources or tool UI metadata for agents to render.

## Our read

Zoom publishes 64 agent skills, the most in this directory, and no MCP server: Ora found no endpoint, manifest or first-party package, which costs 6 points, and the skills index at /.well-known/agent-skills/index.json is the one agent file the domain gets right. The rest of the act layer is thin for a company whose meetings every assistant wants to join, with the API described at docs.zoom.us without a machine-verifiable surface or an OpenAPI specification, neither a CLI nor declared scopes, and a single SDK on npm; OpenID Connect discovery on zoom.us is the surface that counts. Two files are the wrong kind: the llms.txt at docs.zoom.us/.well-known/llms.txt returns an HTML page, and the JSON-LD on the home page describes a Person. The home page itself reads well, 8,293 characters at a 6.7 percent text ratio with one H1, six H2s and thirteen H3s, and five of five sampled pages have text. The server is the gap.

## 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/zoom-agent-readiness/index.md)

## Sources

-   [Ora's scan of zoom.us, GET /api/score (vendor)](https://ora.ai/api/score/zoom.us?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check), read 9 November 2026
-   [Ora's scoring rules, version 2 (vendor)](https://ora.ai/api/ranker/releases/2/rules?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
-   [zoom.us, the company's site](https://www.zoom.com/), read 9 November 2026

Last reviewed 9 November 2026