RoxyAPI Docs MCP Server (keyless, for coding agents)
REMOTE · ROXYAPI.COM
Keyless docs search so coding agents wire up RoxyAPI: every endpoint, param and SDK call.
Available components
Last scanned (24 minutes ago)
Scores higher than 97% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Code Search and Documentation
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 315 tokens (~315/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Tools include usage examples.Pass
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 20 Oct 26 −1
- Tool “search_docs” rewrote its description, which is the text the model reads security
- 3 Oct 26 0
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- 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
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 234 → 313 ▼ functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Sept 26 0
- Tool “search_docs” now declares an output schema ▲ functional
- First check of Tool coverage: 100 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 15 Aug 26 0
- Authorization: unverified → partial ▲ security
- Schema quality: 296 → 234 ▲ functional
- Schema quality: fail → pass ▲ functional
- “search_docs” reworded the description of “compact” cosmetic
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 5 Nov 2026 · Probed https://roxyapi.com/mcp/docs
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=roxyapi.com | CN=WE1,O=Google Trust Services,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | b253589252f3f4620e758a7554771c71 |
| SANs: roxyapi.com, *.roxyapi.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of roxyapi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| roxyapi.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'inline-speculation-rules' 'unsafe-eval' https://challenges.cloudflare.com https://cdn.jsdelivr.net https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self'; connect-src 'self' https://challenges.cloudflare.com https://cloudflareinsights.com; frame-src 'self' https://challenges.cloudflare.com https://roxyapi.github.io; frame-ancestors 'none'; object-src 'none'; base-uri 'self'; form-action 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(self), usb=(), bluetooth=(), accelerometer=(), gyroscope=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://roxyapi.com/mcp/docs | Verified | 200 | |
| http (plaintext) | http://roxyapi.com/mcp/docs | HTTPS enforced | 301 | https://roxyapi.com/mcp/docs |
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 →
search_docs ~238
Search the RoxyAPI knowledge base and get back ranked documentation snippets, each with a source URL. It covers API endpoints with their request and response fields, SDK usage for TypeScript, Python, PHP, C#, Go, and Rust, the WordPress plugin, authentication and API keys, UI components, and step by step integration guides. Call this first whenever you need to integrate RoxyAPI into an app: to find which endpoint or SDK method to use, what parameters a call takes, how to authenticate, or how to wire a feature end to end. Pass the user question verbatim as `query`. If the first results miss, rephrase once and retry.
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | – | Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens. |
| limit | number | – | Max hits to return. Default 10, capped at 25. |
| query | string | yes | User question or keywords. Free text. The whole question works better than guessed keywords. |
| Name | Type | Req | Description |
|---|---|---|---|
| hits | array | yes | – |
{"query":"how do I authenticate an API request"}How do I install the RoxyAPI Docs MCP Server (keyless, for coding agents) server?
RoxyAPI Docs MCP Server (keyless, for coding agents) is a hosted endpoint at https://roxyapi.com/mcp/docs, 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 · roxyapi.com
claude mcp add --transport http com-roxyapi-docs 'https://roxyapi.com/mcp/docs'
What is the RoxyAPI Docs MCP Server (keyless, for coding agents) server?
RoxyAPI Docs MCP Server (keyless, for coding agents) is listed in the public MCP registry as com.roxyapi/docs. Keyless docs search so coding agents wire up RoxyAPI: every endpoint, param and SDK call. This page covers its hosted endpoint (https://roxyapi.com/mcp/docs).
Is the RoxyAPI Docs MCP Server (keyless, for coding agents) server safe to use?
RoxyAPI Docs MCP Server (keyless, for coding agents) scores 89 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 RoxyAPI Docs MCP Server (keyless, for coding agents) server expose?
RoxyAPI Docs MCP Server (keyless, for coding agents) exposes 1 tool: search_docs. Their descriptions and schemas cost roughly 238 tokens of context every time the server is loaded.
Does the RoxyAPI Docs MCP Server (keyless, for coding agents) server require authentication?
No. We connected to RoxyAPI Docs MCP Server (keyless, for coding agents) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RoxyAPI Docs MCP Server (keyless, for coding agents) server still maintained?
RoxyAPI Docs MCP Server (keyless, for coding agents) 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.