DevExpress Documentation
REMOTE · API.DEVEXPRESS.COM
Streamable HTTP MCP server for DevExpress documentation search and retrieval.
Available components
Last scanned (5 hours ago)
Scores higher than 95% of remote servers
Reachable. Last reached 6 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 602 tokens (~301/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 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
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 10 Oct 26 −1
- Schema quality: 153 → 301 ▼ functional
- Schema quality: good → excellent functional
- 2 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 189 → 153 ▲ functional
- Schema quality: excellent → good functional
- 30 Sept 26 0
- Server version: 1.29.1 → 1.30.0 functional
- 28 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- Server version: 1.28.1 → 1.29.1 functional
- Tool “devexpress_docs_get_content” changed its title: Get DevExpress Documentation Content cosmetic
- Tool “devexpress_docs_search” changed its title: Search DevExpress Documentation cosmetic
- 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
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 Nov 2026 · Probed https://api.devexpress.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=*.devexpress.com,O=Developer Express Inc.,L=Glendale,ST=California,C=US | CN=GoDaddy TLS Intermediate CA OV - R1v1,O=GoDaddy.com,C=US | 15 Oct 2026 | 31 Mar 2027 | RSA 2048 | SHA256-RSA | f17b1db8ab2f2ab3 |
| SANs: *.devexpress.com, devexpress.com | ||||||
| CN=GoDaddy TLS Intermediate CA OV - R1v1,O=GoDaddy.com,C=US (CA) | CN=GoDaddy TLS Root CA - R1,O=GoDaddy.com,C=US | 28 Aug 2025 | 24 Aug 2040 | RSA 4096 | SHA256-RSA | fd6142d558ad396c14bb970caea7105b |
| CN=GoDaddy TLS Root CA - R1,O=GoDaddy.com,C=US (CA) | CN=Go Daddy Root Certificate Authority - G2,O=GoDaddy.com\, Inc.,L=Scottsdale,ST=Arizona,C=US | 24 Sept 2025 | 31 Dec 2037 | RSA 4096 | SHA256-RSA | 90de6c7fb3b50b3c0617724fc13402ad |
| CN=Go Daddy Root Certificate Authority - G2,O=GoDaddy.com\, Inc.,L=Scottsdale,ST=Arizona,C=US (CA) | OU=Go Daddy Class 2 Certification Authority,O=The Go Daddy Group\, Inc.,C=US | 1 Jan 2014 | 30 May 2031 | RSA 2048 | SHA256-RSA | 1be715 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.devexpress.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| devexpress.com. | No DS | 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 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.devexpress.com/mcp/docs | Verified | 200 | |
| http (plaintext) | http://api.devexpress.com/mcp/docs | HTTPS enforced | 301 | https://api.devexpress.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 →
devexpress_docs_get_content Get DevExpress Documentation Content ~138
Get full document content by URL from DevExpress documentation. Use this tool to retrieve the complete markdown content of a specific documentation page. PREREQUISITE: ALWAYS call `devexpress_docs_search` before using this tool to get valid URLs. The URL parameter must be obtained from the results of the `devexpress_docs_search` tool.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL of a DevExpress documentation article. REQUIRED: This URL must be obtained from a previous call to `devexpress_docs_search` tool. Do not construct URLs using your general knowledge. Example:… |
No output schema declared.
No examples provided.
devexpress_docs_search Search DevExpress Documentation ~186
Search DevExpress documentation for a given technology and a question. If you want to search for multiple technologies, pass them as a list. This tool returns only snippets/excerpts; full content requires a follow-up `devexpress_docs_get_content` call on a chosen URL. ALWAYS call `devexpress_docs_search` before ANY `devexpress_docs_get_content` call in a user request chain.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | Your specific question, phrased in natural language. Describe what you're trying to accomplish and name the relevant controls, APIs, or features. This tool performs semantic search using a text embed… |
| technologies | array | yes | List of DevExpress technologies to search within. Use specific technology names like 'WindowsForms', 'XtraReports', 'OfficeFileAPI' etc. You must choose from the allowed set. |
No output schema declared.
No examples provided.
How do I install the DevExpress Documentation MCP server?
DevExpress Documentation is a hosted endpoint at https://api.devexpress.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 · api.devexpress.com
claude mcp add --transport http com-devexpress-docs 'https://api.devexpress.com/mcp/docs'
What is the DevExpress Documentation MCP server?
DevExpress Documentation is an MCP server listed in the public MCP registry as com.devexpress/docs. Streamable HTTP MCP server for DevExpress documentation search and retrieval. This page covers its hosted endpoint (https://api.devexpress.com/mcp/docs).
Is the DevExpress Documentation MCP server safe to use?
DevExpress Documentation scores 88 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 DevExpress Documentation MCP server expose?
DevExpress Documentation exposes 2 tools: devexpress_docs_search, devexpress_docs_get_content. Their descriptions and schemas cost roughly 324 tokens of context every time the server is loaded.
Does the DevExpress Documentation MCP server require authentication?
No. We connected to DevExpress Documentation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DevExpress Documentation MCP server still maintained?
DevExpress Documentation is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the DevExpress Documentation MCP server?
VerifyMCP ran 13 checks on DevExpress Documentation, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.