DevDocs10
REMOTE · DEVDOCS10.COM
Search and read tested Swift, JavaScript, CSS and HTML docs from DevDocs10.
Available components
Last scanned (15 hours ago)
Scores higher than 63% of remote servers
Reachable. Last reached 23 Oct 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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 246 tokens (~82/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 18 Oct 26 70
First indexed and scored.
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 23 Oct 2026 · Probed https://devdocs10.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=devdocs10.com | CN=WE1,O=Google Trust Services,C=US | 27 Aug 2026 | 25 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 49bcdb88c6e64add0e343e85b67cdb1e |
| SANs: devdocs10.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 devdocs10.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| devdocs10.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://devdocs10.com/mcp | Verified | 200 | |
| http (plaintext) | http://devdocs10.com/mcp | HTTPS enforced | 301 | https://devdocs10.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 →
get_doc Read a DevDocs10 article ~69
Get a DevDocs10 article as Markdown, including tested example output and browser support where available.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Article path from search_docs, e.g. "swift/swift-structs", "/articles/swift/swift-structs", or a full devdocs10.com URL |
No output schema declared.
No examples provided.
list_docs List DevDocs10 articles ~36
List DevDocs10 articles grouped by topic. Without a section, lists the sections and their topic groups.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | – | – |
No output schema declared.
No examples provided.
search_docs Search DevDocs10 ~92
Search DevDocs10 guides (Swift, JavaScript, CSS, HTML) by keywords. Returns the best-matching articles with their paths; read one with get_doc.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 8) |
| query | string | yes | What to look for, e.g. "swift actors" or "css container queries" |
| section | string | – | Optional: limit to one language |
No output schema declared.
No examples provided.
How do I install the DevDocs10 MCP server?
DevDocs10 is a hosted endpoint at https://devdocs10.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 · devdocs10.com
claude mcp add --transport http com-devdocs10-docs 'https://devdocs10.com/mcp'
What is the DevDocs10 MCP server?
DevDocs10 is an MCP server listed in the public MCP registry as com.devdocs10/docs. Search and read tested Swift, JavaScript, CSS and HTML docs from DevDocs10. This page covers its hosted endpoint (https://devdocs10.com/mcp).
Is the DevDocs10 MCP server safe to use?
DevDocs10 scores 72 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 DevDocs10 MCP server expose?
DevDocs10 exposes 3 tools: search_docs, get_doc, list_docs. Their descriptions and schemas cost roughly 197 tokens of context every time the server is loaded.
Does the DevDocs10 MCP server require authentication?
No. We connected to DevDocs10 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DevDocs10 MCP server still maintained?
DevDocs10 is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.