Qt Documentation
REMOTE · QT-DOCS-MCP.QT.IO · SCANNED SEP 24
Search Qt 6 API and product docs (Qt Core, Qt Quick, Qt Creator, Boot to Qt, MCUs).
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 Security57
- 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 call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 625 tokens (~312/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 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
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
How do I install the Qt Documentation MCP server?
Qt Documentation is a hosted endpoint at https://qt-docs-mcp.qt.io/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 · qt-docs-mcp.qt.io
claude mcp add --transport http io-qt-qt-docs-mcp-qt-documentation 'https://qt-docs-mcp.qt.io/mcp'
{
"mcpServers": {
"io-qt-qt-docs-mcp-qt-documentation": {
"url": "https://qt-docs-mcp.qt.io/mcp"
}
}
} {
"servers": {
"io-qt-qt-docs-mcp-qt-documentation": {
"type": "http",
"url": "https://qt-docs-mcp.qt.io/mcp"
}
}
} [mcp_servers.io-qt-qt-docs-mcp-qt-documentation] url = "https://qt-docs-mcp.qt.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-qt-qt-docs-mcp-qt-documentation": {
"type": "remote",
"url": "https://qt-docs-mcp.qt.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-qt-qt-docs-mcp-qt-documentation --url 'https://qt-docs-mcp.qt.io/mcp' --transport streamable-http
mcp_servers:
io-qt-qt-docs-mcp-qt-documentation:
url: "https://qt-docs-mcp.qt.io/mcp" {
"McpServers": {
"io-qt-qt-docs-mcp-qt-documentation": {
"Transport": "http",
"Url": "https://qt-docs-mcp.qt.io/mcp"
}
}
} assistant mcp add io-qt-qt-docs-mcp-qt-documentation -t streamable-http -u 'https://qt-docs-mcp.qt.io/mcp'
{
"mcpServers": {
"io-qt-qt-docs-mcp-qt-documentation": {
"type": "http",
"url": "https://qt-docs-mcp.qt.io/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.
- 26 Aug 26 78
- 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
- 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
- 27 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
- 26 Jul 26 0
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 24 Sept 2026 · Probed https://qt-docs-mcp.qt.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=qt-docs-mcp.qt.io | CN=YE2,O=Let's Encrypt,C=US | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 57a028d8455670d79f9b7fe9e89cc027bce |
| SANs: qt-docs-mcp.qt.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 insecure
Validation of qt-docs-mcp.qt.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| qt.io. | 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://qt-docs-mcp.qt.io/mcp | Verified | 200 | |
| http (plaintext) | http://qt-docs-mcp.qt.io/mcp | HTTPS enforced | 301 | https://qt-docs-mcp.qt.io/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 →
qt_documentation_read ~119
Read the full content of a specific Qt documentation page. Use the filename shown in search results.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Filename of the Qt documentation page. Use ONLY the filename from search results (e.g., 'signalsandslots.html' NOT full paths with version numbers). Module paths like 'qtcore/qobject.html' also work. |
| version | string | – | Optional: Qt version to read from (e.g., '6.10.0', '6.9.0'). Defaults to latest installed version if not specified. |
No output schema declared.
No examples provided.
qt_documentation_search ~422
Call qt_documentation_search when: (a) you're about to claim a signal/slot/property/default exists, (b) the API is in Qt 6.7+ or a non-core module (MQTT, OPC UA, Network Auth, etc), (c) the user used the words 'docs', 'official', 'verify', or 'check'. Skip when: the question is about basic QString/QObject/signal-slot syntax.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Optional: Filter by document type. Default is 'all'. Note: 'function' returns the class reference page that contains the function (there are no function-level pages); for QML, use 'qml'. |
| intent | string | – | Optional: Prioritizes (not filters) results by type. 'api'=class reference, 'tutorial'=how-to guides, 'guide'=overviews, 'concept'=explanations, 'example'=code samples, 'migration'=porting guides. |
| keywords | array | – | Optional: Array of keywords to search for. Results match ANY keyword. Example: ["button", "signal", "connect"]. Alternative to 'query' for better multi-term matching. |
| max_results | integer | – | Optional: Maximum number of results to return (1-10). Default is 3. |
| module | string | – | Optional: Limit search to specific Qt module (e.g., 'qtcore', 'qtwidgets', 'qtqml', 'qtquick', 'qtnetwork') |
| product | string | – | Optional: Limit search to a specific documentation product (e.g. 'qt', 'qtcreator', 'pyside6'). Omit to search all products. |
| query | string | – | Search query for Qt documentation (e.g., 'Animation', 'QTimer', 'signal slot'). Optional if 'keywords' is provided. |
| version | string | – | Optional: Qt version to search (e.g., '6.10.0', '6.9.0'). Defaults to latest installed version if not specified. |
No output schema declared.
No examples provided.
What is the Qt Documentation MCP server?
Qt Documentation is an MCP server listed in the public MCP registry as io.qt.qt-docs-mcp/qt-documentation. Search Qt 6 API and product docs (Qt Core, Qt Quick, Qt Creator, Boot to Qt, MCUs). This page covers its hosted endpoint (https://qt-docs-mcp.qt.io/mcp).
Is the Qt Documentation MCP server safe to use?
Qt Documentation scores 78 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 Qt Documentation MCP server expose?
Qt Documentation exposes 2 tools: qt_documentation_search, qt_documentation_read. Their descriptions and schemas cost roughly 541 tokens of context every time the server is loaded.
Does the Qt Documentation MCP server require authentication?
No. We connected to Qt Documentation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Qt Documentation MCP server still maintained?
Qt Documentation is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.