_ registry / mcp http-sse · checked 4h ago

openai-docs-mcp

https://developers.openai.com

Registry code: 0a94054f905f1d6f

api record

CLI and MCP server for Bugpacker bug packages. Give a coding agent the console, network and repro steps from a real bug, without any of it leaving your machine.

from a public catalogue that lists it, not from the operator

endpoint
https://developers.openai.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is openai-docs-mcp live?
Yes — it answered the hub's last check (checked 4h ago). It answered 98% of checks over the last 30 days.
Is openai-docs-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does openai-docs-mcp have?
5 tools: get_openapi_spec, search_openai_docs, fetch_openai_doc, list_api_endpoints, list_openai_docs.
Is openai-docs-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98%

90 days 97.9%· all time 97.9%

latency
154ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 336 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
knowledge & reference documentation & docs search
used for
  • search openai developer docs
  • fetch an openai doc page
  • get openapi spec for an endpoint
  • list openai api endpoints
takes → gives
text → text, data
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
2 open 3 never probed 2 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_api_endpoints reads open 20h ago

    List all OpenAI API endpoint URLs available in the OpenAPI spec.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • list_openai_docs reads open 20h ago

    List or browse pages from `platform.openai.com`, `developers.openai.com`, and `learn.chatgpt.com` that this server crawls (useful when you don’t know the right query yet or you’re paging through results). Use this whenever you are working with the OpenAI API (including the Responses API), OpenAI API SDKs, plugins, ChatGPT, or Codex. Results include URLs—**after `list`, use `fetch_openai_doc`** on a result URL to get the full markdown.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1
    },
    "cursor": {
      "type": "string"
    }
  }
}
    arguments 14 lines
  • get_openapi_spec reads unknown 20h ago

    Return the OpenAPI spec for a specific API endpoint URL. Optionally filter code samples by language, or return only code samples.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "minLength": 1
    },
    "languages": {
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1
      }
    },
    "codeExamplesOnly": {
      "type": "boolean"
    }
  }
}
    arguments 23 lines
  • search_openai_docs reads unknown 12h ago

    Search across `platform.openai.com`, `developers.openai.com`, and `learn.chatgpt.com` docs. Use this whenever you are working with the OpenAI API (including the Responses API), OpenAI API SDKs, plugins, ChatGPT, or Codex. Results include URLs—**after `search`, use `fetch_openai_doc`** to read/quote the exact markdown.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "minLength": 1
    },
    "cursor": {
      "type": "string"
    }
  }
}
    arguments 21 lines
  • fetch_openai_doc reads unknown 12h ago

    Fetch the markdown for a specific doc page from `developers.openai.com`, `platform.openai.com`, or `learn.chatgpt.com` so you can quote or summarize exact, up-to-date guidance (schemas, examples, limits, and edge cases). Prefer to **`search_openai_docs` first** (or `list_openai_docs` if you’re browsing) to find the best URL, then `fetch_openai_doc` to pull the exact text; you can pass `anchor` (for example, `#streaming`) to fetch just that section.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "minLength": 1
    },
    "anchor": {
      "type": "string"
    }
  }
}
    arguments 16 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 0a94054f905f1d6f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0a94054f905f1d6f/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/0a94054f905f1d6f/badge.svg)](https://brick.blue/agent/0a94054f905f1d6f?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.