# Redocly (remote · redocly.com)

Search and read the Redocly product docs, guides and blog on redocly.com, and report a wrong page.

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `redocly.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/com-redocly-mcp/redocly.md), [page](https://verifymcp.io/servers/com-redocly-mcp/redocly)

## Channel facts

- Endpoint: `https://redocly.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1580 tokens (~158/item across 10 items; 3 tools + 7 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (67% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Redocly MCP server?

Redocly is a hosted endpoint at https://redocly.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-redocly-mcp 'https://redocly.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-redocly-mcp": {
      "url": "https://redocly.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-redocly-mcp": {
      "type": "http",
      "url": "https://redocly.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-redocly-mcp]
url = "https://redocly.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-redocly-mcp": {
      "type": "remote",
      "url": "https://redocly.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-redocly-mcp --url 'https://redocly.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-redocly-mcp:
    url: "https://redocly.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-redocly-mcp": {
      "Transport": "http",
      "Url": "https://redocly.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-redocly-mcp -t streamable-http -u 'https://redocly.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-redocly-mcp": {
      "type": "http",
      "url": "https://redocly.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 82, +1)

- [functional] Server version: 0.1.27 → 0.1.30

### 2026-11-03 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 79, 0)

- [functional] Server version: 0.1.25 → 0.1.27

### 2026-10-30 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 78, 0)

- [security] Tool “execute” rewrote its description, which is the text the model reads
- [functional] Server version: 0.1.24 → 0.1.25

### 2026-10-27 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 77, 0)

- [functional] Server version: 0.1.23 → 0.1.24

## MCP tools (3)

### `execute` (~382 tokens)

Query the docs with code

Run plain JavaScript (no TypeScript syntax) in a sandbox against the documentation at https://redocly.com. The script calls the sandbox functions on the global `site` object.
The only extra global is `site` - there is no `fetch`, `console`, `setTimeout`, `require`, or Node.js API; all I/O goes through `site`.

Workflow - minimize round-trips; one `discover` call plus one `execute` call covers most requests:
1\. Analyze the request and decide which sandbox functions it needs.
2\. Call `discover` with those names to get their exact TypeScript signatures - inputs, result shapes, and a worked example. NEVER call `execute` with guessed function 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 function calls, pass one call's output into the next, process results in plain JavaScript, and `return` only what the request needs.

Functions for `execute` scripts (signatures come from `discover`):
\- listApis — List the available APIs.
\- getEndpoints — Get all endpoints for an API.
\- getEndpointInfo — Get the details of an endpoint.
\- getSecuritySchemes — Get the security schemes for an API.
\- getFullApiDescription — Get the complete OpenAPI description.
\- search — Search the documentation.
\- listPages — List the docs navigation, one level per call.
\- getPage — Read a docs page as Markdown, in line windows.
\- grepPages — Find the docs lines that contain a text.

Input parameters:

- `code` (string, required): JavaScript to run in the sandbox. Return a value to receive it as the result.
- `description` (string, required): A short, human-readable summary of what this code does.

Output parameters:

- `error` (string): Why the code failed. Set only on a failed call
- `result`: The value the code returned, as JSON
- `sentFetches` (array): Every `fetch` request that reached an API before the failure, with its status; running the code again sends them again. Set only on a failed call

### `discover` (~151 tokens)

Get docs function signatures

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

Input parameters:

- `names` (array): Names of the sandbox functions to discover: listApis, getEndpoints, getEndpointInfo, getSecuritySchemes, getFullApiDescription, search, listPages, getPage, grepPages. Omit to discover all of them.

### `submit-feedback` (~132 tokens)

Submit feedback

Report a documentation page that is wrong or incomplete. Use it when the user reports a problem with a page on this site, or agrees to report a problem that you found. Do not use it for product bugs or support questions.

Input parameters:

- `details` (string): Expected versus actual behavior, missing steps, or the snippet that failed
- `path` (string, required): Path or URL of the documentation page the feedback is about (e.g. /guides/auth)
- `summary` (string, required): One sentence that names what is wrong with the page
- `targetFeature` (string): The API or feature the page documents

Output parameters:

- `message` (string)
- `page` (string)
- `status` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-redocly-mcp/redocly#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78
- 2026-10-28: 78
- 2026-10-27: 78
- 2026-10-26: 77
- 2026-10-25: 77
- 2026-10-24: 76
- 2026-10-23: 76
- 2026-10-22: 75
- 2026-10-21: 75
- 2026-10-20: 74

## Common questions

### What is the Redocly MCP server?

Redocly is an MCP server listed in the public MCP registry as com.redocly/mcp. Search and read the Redocly product docs, guides and blog on redocly.com, and report a wrong page. This page covers its hosted endpoint (https://redocly.com/mcp).

### Is the Redocly MCP server safe to use?

Redocly scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Redocly MCP server expose?

Redocly exposes 3 tools: execute, discover, submit-feedback. Their descriptions and schemas cost roughly 665 tokens of context every time the server is loaded.

### Does the Redocly MCP server require authentication?

No. We connected to Redocly without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Redocly MCP server still maintained?

Redocly is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://redocly.com/mcp
- Repository: https://github.com/Redocly/redocly-plugin
- Website: https://redocly.com/docs/platform/ai-ready/use-redocly-with-ai-clients
- Changelog RSS feed: https://verifymcp.io/servers/com-redocly-mcp/redocly.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-redocly-mcp/redocly.json
- HTML version of this page: https://verifymcp.io/servers/com-redocly-mcp/redocly