# MCP metadata inspection: openai-docs

Endpoint: https://developers.openai.com/mcp
Official source: https://developers.openai.com/learn/docs-mcp (reviewed 2026-10-15)
Documented profile: Public read-only documentation endpoint; documented setup supplies a URL without credentials
Observed: 2026-10-15T07:14:22.147Z
Run: a4e8181f-679c-4023-917f-11ee2482fee4 (completed)
Protocol: requested 2025-11-25; server reported 2025-11-25; negotiated 2025-11-25
Coverage: 4/5 checks attempted; 4 passed, 0 failed, 0 unknown, 1 not tested, 0 not applicable.
Catalog: 5 observed tools; complete-catalog. SHA-256: 5ad0dafb4c06251c121eee0ad28ef8b90349d555f66cfdba92d9b372359bef24.

- **protocol-negotiation: passed**. Negotiated protocol 2025-11-25; this does not establish host compatibility.
- **initialized-notification: passed**. The initialization notification received HTTP 202 with an empty body.
- **tool-catalog: passed**. Observed the complete advertised catalog: 5 tools across 1 pages.
- **tool-metadata-shape: passed**. SDK metadata shape checked for 5 observed tools. This is not complete JSON Schema validation or behavior verification.
- **oauth-login: not-tested**. OAuth discovery, login, token refresh and authenticated access are outside this anonymous inspection.

- metadata: **passed**
- authenticatedExecution: **not-tested**
- modelApi: **not-tested**
- chatgptHost: **not-tested**
- claudeHost: **not-tested**
- publicationApproval: **not-tested**

Tool executions: **0**. This report contains metadata observations only.

- Metadata-only anonymous inspection. No tools/call, OAuth flow, API model calls, host UI or publication review was executed. No global quality or safety score is produced.
- Annotations are server declarations, not verified behavior. Metadata success does not establish task success, security, usefulness or ChatGPT/Claude compatibility.
- Only active exact HTTPS endpoints in the reviewed source registry are accepted. Redirects, supplied credentials, arbitrary endpoints and OAuth URL fetching are disabled. DNS/TLS use the local runtime: this is not a hardened multi-tenant SSRF sandbox and must not be exposed as a public scanner.
- Session identifiers are used only in memory. Request/response headers, raw error messages, raw descriptions and schemas are excluded from artifacts. Tool names and aggregate metadata remain untrusted server input.
- Only the recorded protocol versions and bounded catalog prefix are supported. Reaching a bound or lacking access means unknown, not a failed server or a passing full audit.