_ registry / mcp + a2a http-sse · checked 2h ago

Docs MCP server

https://cafe.redocly.com

Registry code: 9069e3fd42d10924

api record

This server exposes documentation tools (API discovery, endpoint details, security schemes, full-text search) through `describe-tools` and `execute`:

- `describe-tools` returns the exact TypeScript signatures of the sandbox tools.

endpoint
https://cafe.redocly.com/mcp
door code
aae1d612ff9f056f
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 Docs MCP server live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is Docs MCP server free to use?
Yes — the hub reached it with no key and no payment.
What tools does Docs MCP server have?
5 tools: execute, submit-feedback, manageApiCredentials, createAnonymousSession, describe-tools.
Is Docs MCP server 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
99.7%

90 days 99.8%· all time 100%

latency
480ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 577 checks · signed record
  • degraded → live
  • live → degraded· endpoint unreachable (timeout after 20000ms); card still served
  • degraded → live
_ what it is for
used for
  • search api documentation
  • get endpoint details and security schemes
takes → gives
text → text, data
tools
2 reads
note
documentation mirror
_ 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
1 open 4 never probed 1 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.

  • describe-tools reads open 2h ago

    Get the exact TypeScript signatures of the sandbox tools available to `execute`. Analyze the user request first, then pass `tools` with only the tool names the request needs (every name is listed in this input schema / description); omit `tools` only when you cannot tell which tools apply. Always call this before your first `execute` and never guess signatures. Request every tool the task may need in ONE call instead of calling this repeatedly.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "tools": {
          "type": "array",
          "items": {
            "enum": [
              "listApis",
              "getEndpoints",
              "getEndpointInfo",
              "getSecuritySchemes",
              "getFullApiDescription",
              "search",
              "fetch"
            ],
            "type": "string"
          },
          "nullable": true,
          "description": "Tool names to describe: listApis, getEndpoints, getEndpointInfo, getSecuritySchemes, getFullApiDescription, search, fetch. Omit to describe everything."
        }
      },
      "additionalProperties": false
    }
    arguments 24 lines
  • execute reads unknown never probed

    Run JavaScript in a sandbox against the tools for the documentation at https://cafe.redocly.com. The tools are on the global `tools` object. The extra globals are `tools`, `fetch`, `URL`, `URLSearchParams`, and `FormData` - there is no `console`, `setTimeout`, `require`, or Node.js API; all other I/O goes through `tools`. Workflow - minimize round-trips; one `describe-tools` call plus one `execute` call covers most requests: 1. Analyze the request and decide which sandbox tools it needs. 2. Call `describe-tools` with those names to get their exact TypeScript signatures - inputs, result shapes, and a worked example. NEVER call `execute` with guessed method names, parameter names, enum values, or result field names: read fields off the declared return types, not from assumptions. 3. Batch everything into a SINGLE script: chain tool calls, pass one call's output into the next, process results in plain JavaScript, and `return` only what the request needs. Available tools (exact signatures come from `describe-tools`): - listApis — Lists the APIs documented in this project - getEndpoints — Get all endpoints for a specific API. When several definiti… - getEndpointInfo — Get comprehensive information about specific endpoint inclu… - getSecuritySchemes — Get the security schemes for a specific API. When several d… - getFullApiDescription — Get the complete OpenAPI description. When several definiti… - search — Search across the documentation to fetch relevant content f… - fetch — Call the documented APIs over HTTP

    mcp-tool

    {
      "type": "object",
      "required": [
        "code",
        "description"
      ],
      "properties": {
        "code": {
          "type": "string",
          "minLength": 1,
          "description": "JavaScript to run in the sandbox. Return a value to receive it as the result."
        },
        "description": {
          "type": "string",
          "minLength": 1,
          "description": "A short, human-readable summary of what this code does."
        },
        "sessionHandle": {
          "type": "string",
          "minLength": 1,
          "description": "Handle returned by createAnonymousSession. Required when an API needs credentials. This parameter is only offered when createAnonymousSession is available, so pass it whenever you have called that tool."
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • submit-feedback unknown never probed

    Report a documentation page that is wrong or incomplete

    mcp-tool

    {
      "type": "object",
      "required": [
        "path",
        "summary"
      ],
      "properties": {
        "path": {
          "type": "string",
          "maxLength": 1000,
          "minLength": 1,
          "description": "Path or URL of the documentation page the feedback is about (e.g. /guides/auth)"
        },
        "details": {
          "type": "string",
          "nullable": true,
          "maxLength": 4000,
          "description": "Expected versus actual behavior, missing steps, or the snippet that failed"
        },
        "summary": {
          "type": "string",
          "maxLength": 500,
          "minLength": 1,
          "description": "One sentence that names what is wrong with the page"
        },
        "targetFeature": {
          "type": "string",
          "nullable": true,
          "maxLength": 500,
          "description": "The API or feature the page documents"
        }
      },
      "additionalProperties": false
    }
    arguments 34 lines
  • manageApiCredentials unknown never probed

    Get a secure link where the user sets, replaces, or removes the credentials this server sends to a documented API. Call it when the user wants to change or clear an API key, or when a tool result tells you the stored credentials were rejected. The link covers every credential the API accepts, so scheme is optional - pass it only when a tool result names the scheme that was rejected. It returns a link for the user to open - never ask for the secret in the conversation and never pass it as an argument.

    mcp-tool

    {
      "type": "object",
      "required": [
        "api"
      ],
      "properties": {
        "api": {
          "enum": [
            "openapi/cafe.yaml",
            "Redocly Cafe"
          ],
          "type": "string",
          "minLength": 1,
          "description": "The API to manage credentials for: its `filePath` or the `name` from `listApis`. The file paths are: openapi/cafe.yaml."
        },
        "scheme": {
          "type": "string",
          "minLength": 1,
          "description": "Name of the security scheme to manage the credential for, as named in the API description (a tool result that reports a rejected credential names it). Omit it to let the link cover every scheme the API accepts."
        },
        "sessionHandle": {
          "type": "string",
          "minLength": 1,
          "description": "Handle returned by createAnonymousSession. Required while the caller is anonymous, so the credentials are stored against the same subject the API calls use."
        }
      },
      "additionalProperties": false
    }
    arguments 28 lines
  • createAnonymousSession unknown never probed

    Create an anonymous session handle for storing upstream API credentials. Pass the returned sessionHandle to execute when an API needs credentials and the caller is not signed in. Treat it as a secret and reuse it across calls.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
_ try it over mcp 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 9069e3fd42d10924.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/9069e3fd42d10924/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/9069e3fd42d10924/badge.svg)](https://brick.blue/agent/9069e3fd42d10924?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 knowoff the mcp door
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.

_ also on redocly.com 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.