com.redpanda/docs-mcp
REMOTE · DOCS.REDPANDA.COM · SCANNED OCT 4
Get authoritative answers about Redpanda documentation and search API references.
Available components
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. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the com.redpanda/docs-mcp server?
com.redpanda/docs-mcp is a hosted endpoint at https://docs.redpanda.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.
remote · docs.redpanda.com
claude mcp add --transport http com-redpanda-docs-mcp 'https://docs.redpanda.com/mcp'
{
"mcpServers": {
"com-redpanda-docs-mcp": {
"url": "https://docs.redpanda.com/mcp"
}
}
} {
"servers": {
"com-redpanda-docs-mcp": {
"type": "http",
"url": "https://docs.redpanda.com/mcp"
}
}
} [mcp_servers.com-redpanda-docs-mcp] url = "https://docs.redpanda.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-redpanda-docs-mcp": {
"type": "remote",
"url": "https://docs.redpanda.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-redpanda-docs-mcp --url 'https://docs.redpanda.com/mcp' --transport streamable-http
mcp_servers:
com-redpanda-docs-mcp:
url: "https://docs.redpanda.com/mcp" {
"McpServers": {
"com-redpanda-docs-mcp": {
"Transport": "http",
"Url": "https://docs.redpanda.com/mcp"
}
}
} assistant mcp add com-redpanda-docs-mcp -t streamable-http -u 'https://docs.redpanda.com/mcp'
{
"mcpServers": {
"com-redpanda-docs-mcp": {
"type": "http",
"url": "https://docs.redpanda.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Sept 26 −41
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 14 Aug 26 0
- Stability: 0.60 → fail ▼ security
- Tool “ask_redpanda_question” rewrote its description, which is the text the model reads security
- Schema quality: 256 → 295 ▼ functional
- “ask_redpanda_question” changed the type of “top_k”: number → integer ▼ functional
- Tool coverage: 85% → 93% ▲ functional
- Server version: 1.1.3 → 1.2.0 functional
- “ask_redpanda_question” added an optional parameter “platform” cosmetic
- “ask_redpanda_question” reworded the description of “top_k” cosmetic
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Oct 2026 · Probed https://docs.redpanda.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=docs.redpanda.com | CN=YE1,O=Let's Encrypt,C=US | 26 Sept 2026 | 25 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5b75436a8f06886603ab0d4cbbafa0b3256 |
| SANs: docs.redpanda.com, docs.vectorized.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of docs.redpanda.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| redpanda.com. | present | 2371 | 13 | Verified |
| docs.redpanda.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://docs.redpanda.com/mcp | Verified | 200 | |
| http (plaintext) | http://docs.redpanda.com/mcp | HTTPS enforced | 301 | https://docs.redpanda.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ask_redpanda_question Search Redpanda Sources ~387
Search the official Redpanda documentation and return the most relevant sections from it for a user query. Each returned section includes the url and its actual content in markdown. Use this tool for all queries that require Redpanda knowledge. Results are ordered by relevance, with the most relevant result returned first. If you know the user's deployment platform, pass "platform" so results from the other platform's docs are excluded. Note that "platform" filters the sections already retrieved rather than re-running the search, so it can return substantially fewer sections: on a broker-level question where most matches come from the other platform's docs, it can cut a 15-section response to 1 or 2. Omit "platform" if you would rather have more context and judge platform relevance yourself from each section's url.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| platform | string | – | The user's deployment platform. 'cloud' excludes Self-Managed sections; 'self-managed' excludes Redpanda Cloud sections. Platform-neutral docs (Connect, API reference, labs) are always kept. Applied… |
| question | string | yes | – |
| top_k | integer | – | Maximum number of sections to return, applied after platform filtering. Must be a positive integer. |
No output schema declared.
No examples provided.
get_api_reference_content Get API Reference Content ~215
Retrieve full content of API reference pages by URL. Returns complete endpoint details including parameters, request/response schemas, and examples. Use this after finding pages via list_api_reference_pages or search_api_reference. Pass the URLs from those results directly. Returns up to 10 pages per request. URLs must be from docs.redpanda.com/api/doc/*.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| urls | array | yes | Page URLs to retrieve (max 10). Use URLs from list_api_reference_pages or search_api_reference results. |
No output schema declared.
No examples provided.
get_more_tools ~53
Check for additional tools whenever your task might benefit from specialized capabilities - even if existing tools could work as a fallback.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A description of your goal and what kind of tool would help accomplish it. |
No output schema declared.
No examples provided.
list_api_reference_pages List API Reference Pages ~349
List pages in Redpanda API reference documentation. Returns endpoints, schemas, and topic pages with URL, title, type, and description. SCOPING (important for accurate results): - api="all" or omit: Lists all available APIs - api="admin": Cluster management operations (brokers, partitions, configs, users) - api="cloud-controlplane": Redpanda Cloud resource management (clusters, networks, namespaces) - api="cloud-dataplane": Cloud cluster data operations (topics, ACLs, connectors) - api="http-proxy": Kafka operations over HTTP (produce, consume, offsets) - api="schema-registry": Schema management (register, retrieve, compatibility) Use this to browse API structure. For general Redpanda docs, use ask_redpanda_question instead.
| Name | Type | Req | Description |
|---|---|---|---|
| api | string | – | Which API to list: "all" or omit for overview of all APIs, or a specific API name (admin, cloud-controlplane, cloud-dataplane, http-proxy, schema-registry) |
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| url | string | – | Specific URL path to list children of (optional, defaults to API root) |
No output schema declared.
No examples provided.
search_api_reference Search API Reference ~471
Search Redpanda API reference documentation by keyword. Returns up to 20 matching endpoints, schemas, or topics with URL, title, and text excerpts. SCOPING (important for accurate results): - api="all" or omit: Search across ALL APIs at once - useful when unsure which API contains the endpoint - api="admin": Search only cluster management (brokers, partitions, configs, users, maintenance) - api="cloud-controlplane": Search only Cloud resource management (clusters, networks, namespaces) - api="cloud-dataplane": Search only Cloud data operations (topics, ACLs, connectors) - api="http-proxy": Search only HTTP Proxy (produce, consume, offsets over HTTP) - api="schema-registry": Search only Schema Registry (register, retrieve, compatibility) WHEN TO USE WHICH: - User asks "broker endpoints" → api="admin" (brokers are cluster management) - User asks "create topic API" → api="all" (topics exist in admin AND cloud-dataplane) - User asks "Cloud cluster API" → api="cloud-controlplane" - User asks about Redpanda APIs generally → api="all" or omit For general Redpanda questions (not API-specific), use ask_redpanda_question instead.
| Name | Type | Req | Description |
|---|---|---|---|
| api | string | – | Scope: "all" or omit to search all APIs, or specific API name (admin, cloud-controlplane, cloud-dataplane, http-proxy, schema-registry) |
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| query | string | yes | Search keywords (e.g., "broker", "create topic", "ACL") |
| type | string | – | Filter by type: operation (endpoints), schema (data types), topic (guides), authentication, webhook |
No output schema declared.
No examples provided.
What is the com.redpanda/docs-mcp server?
com.redpanda/docs-mcp is listed in the public MCP registry as com.redpanda/docs-mcp. Get authoritative answers about Redpanda documentation and search API references. This page covers its hosted endpoint (https://docs.redpanda.com/mcp).
Is the com.redpanda/docs-mcp server safe to use?
com.redpanda/docs-mcp scores 36 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 com.redpanda/docs-mcp server expose?
com.redpanda/docs-mcp exposes 5 tools: ask_redpanda_question, list_api_reference_pages, search_api_reference, get_api_reference_content, get_more_tools. Their descriptions and schemas cost roughly 1,475 tokens of context every time the server is loaded.
Does the com.redpanda/docs-mcp server require authentication?
No. We connected to com.redpanda/docs-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.redpanda/docs-mcp server still maintained?
com.redpanda/docs-mcp is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.