_ registry / mcp + a2a HTTP+JSON · checked 2h ago

Redocly

https://redocly.com

Registry code: 8ef0a5fa00faafb1

api record

Tools for the documentation at https://redocly.com. Use them to answer questions about the content of these docs.

- `discover` returns the exact TypeScript signatures of the sandbox functions.

endpoint
https://redocly.com/a2a
door code
021e45ee1023a3f9
protocol
HTTP+JSON ·0.3
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 Redocly live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is Redocly free to use?
Yes — the hub reached it with no key and no payment.
What tools does Redocly have?
7 tools: redocly, redocly-cli, recheck-config, recheck-lint, redocly-api-docs, redocly-authoring, redocly-lint-rules.
Is Redocly 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.5%

90 days 99.5%· all time 99.3%

latency
210ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 743 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
used for
  • search api documentation
  • get endpoints of an api
  • get full openapi description
takes → gives
text → text
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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred from the card: it declares no security schemes; the endpoint did not answer the protocol directly

_ what it can do 7 tools
7 never probed 0 of 7 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.

  • redocly unknown never probed

    Set up, write, preview, and publish documentation with Redocly, and work on existing Redocly projects. Use when the user wants to set up Redocly in a repository, create a docs site, document an API from an OpenAPI, AsyncAPI, or GraphQL description, preview docs locally, publish through the Redocly platform, clone a Redocly-hosted project, or run Redocly CLI. Also use when editing a project with redocly.yaml, sidebars.yaml, or a @theme folder, and when unsure which Redocly skill applies.

  • redocly-cli unknown never probed

    Redocly CLI for OpenAPI, AsyncAPI, Arazzo, and Overlay descriptions, and for Markdown docs. Use when the user wants to lint, bundle, split, or join an API description, apply decorators or overlays, build or preview API docs, lint Markdown or prose with recheck, test a live API with respect or Arazzo, capture traffic or check drift, get stats or a score, generate a TypeScript client, document an MCP server in an OpenAPI description, push to the Redocly platform, clone a Redocly-hosted project and open its pull requests, or find the node type a rule or plugin should target.

  • recheck-config unknown never probed

    Use when you create or tune the recheck block and recheck/* presets in redocly.yaml for a project — choose presets, set severities from measured counts, add exceptions, adopt a baseline, and validate the result.

  • recheck-lint unknown never probed

    Use when you write or edit Markdown in a project whose redocly.yaml has a recheck block or a recheck/* preset in extends — run redocly recheck on the touched files before you commit them or hand them over, and fix what it finds.

  • redocly-api-docs unknown never probed

    Use when adding or changing API reference docs in a Redocly project: rendering an OpenAPI, AsyncAPI, GraphQL, or SOAP (WSDL) description, its URL and place in the sidebar or navbar, code samples, the Try it (Replay) console, the mock server, x- extensions such as x-tagGroups or x-codeSamples, or embedding one operation or schema in a Markdown page. Not for linting, bundling, or splitting API descriptions (use redocly-cli).

  • redocly-authoring unknown never probed

    Use when writing or changing content in a Redocly project: adding, moving, or renaming pages, choosing file names and URLs, links and images, page titles and front matter, Markdoc tags such as admonitions, tabs, cards, code groups, and partials, the sidebar, navbar, and footer, or site settings in redocly.yaml. Not for API reference docs from OpenAPI, AsyncAPI, or GraphQL files (use redocly-api-docs).

  • redocly-lint-rules unknown never probed

    Implement a Redocly CLI lint rule in a user's redocly.yaml or custom plugin for an OpenAPI, AsyncAPI, or Arazzo description. Use when the user wants a convention enforced, asks for a configurable rule or a plugin rule, debugs a rule that never reports or gives false positives, or migrates rules from another linter such as Spectral.

_ try it over a2a 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 8ef0a5fa00faafb1.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8ef0a5fa00faafb1/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/8ef0a5fa00faafb1/badge.svg)](https://brick.blue/agent/8ef0a5fa00faafb1?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
70%

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.