Qt Documentation MCP (official, remote)
Capped at 65: vendor-hosted, source not published. The tests add up to 80.
Test points add up to 80; the score is capped at 65 (vendor-hosted, source not published). Not a quality or security rating. Capped listings are not promoted in our rankings or on the homepage. Why scores are capped
Test points before the cap (80/100)
- Install20/20
- Handshake30/30
- Maintenance15/25
- Docs15/15
- License0/10
Vendor-hosted
Tested The Qt Company's hosted documentation MCP at https://qt-docs-mcp.qt.io/mcp (server qt-docs-server 0.3.0; registry io.qt.qt-docs-mcp/qt-documentation, latest 0.4.0). Initialize and tools/list worked with no account using protocol 2025-11-25 (2 read-only tools). Real calls: qt_documentation_search for 'QTimer singleShot' returned Qt 6.12 matches and qt_documentation_read returned the QTimer page. Compatibility: Qt's server rejects initialize with HTTP 400 (empty body) when the client sends the MCP-Protocol-Version header as 2025-06-18 (2025-03-26 in that header is rejected the same way). It answers when the header is 2025-11-25 or absent, and always negotiates 2025-11-25, so 2025-03-26 works only as the initialize body version with no header. Clients that pin 2025-06-18 in the header may fail to connect. Our rubric has no compatibility deduction, so this is a note, not a score change. Vendor-hosted, no public source: 65 cap, not source-audited.
Tool-call test (2026-11-11, direct MCP stdio client, no LLM): pass. 2 of 2 read calls passed anonymously (protocol 2025-11-25). Evidence: live endpoint probe, Nov 11, 2026.
Qt-hosted endpoint. Initialize and tools/list worked without sign-in using protocol 2025-11-25 (2 read-only tools); both returned content. Compatibility: initialize returns HTTP 400 when the client sends an MCP-Protocol-Version header of 2025-06-18 (also 2025-03-26). Source isn't public: vendor-hosted 65 cap (Our review, Nov 11, 2026).
Maintenance date 2026-10-01: date from page metadata (JSON-LD BlogPosting dateModified 2026-10-01T08:37:30.593Z (datePublished 2026-05-12T06:29:42.000Z)) of https://www.qt.io/blog/introducing-the-mcp-tool-for-qt-documentation, fetched 2026-11-11T08:34Z. Not a changelog entry.
Sources: https://doc.qt.io/agentictools/mcp/setup-manual/ · https://www.qt.io/blog/introducing-the-mcp-tool-for-qt-documentation · https://registry.modelcontextprotocol.io/v0/servers?search=io.qt.qt-docs-mcp/qt-documentation
Transport (tested 2026-11-11): Streamable HTTP
Token cost (estimate): approx. 783 tokens, cl100k estimate (2 tools, measured 2026-11-11). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 2 read, 0 write (state-changing), 0 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown
Auth: none. Rate limit: unknown. Pricing unit: unknown.
qt_documentation_read— readqt_documentation_search— read
remote handshake listed tools without credentials; no recorded key or OAuth
Score 65/100 · Tools 2 · Token cost approx. 783 tokens · Compare · Last tested 2026-11-11 · Server version 0.3.0 · Remote endpoint https://qt-docs-mcp.qt.io/mcp (streamable-http)
Summary: Qt Documentation MCP (official, remote) completed an MCP handshake without credentials and exposed 2 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 2
- Context cost
- approx. 783 tokens, cl100k estimate (2 tools, measured 2026-11-11; an estimate) ranking · add up your servers' context cost
- Login
- No key needed for the tools we called
- Tested
- 2026-11-11
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | Endpoint https://qt-docs-mcp.qt.io/mcp reachable over streamable-http (HTTP 200) in 0.8s; no install step for remote servers. |
| handshake | pass | 30 | MCP initialize (protocol 2025-11-25, server qt-docs-server 0.3.0) + tools/list over streamable-http succeeded with no credentials; 2 tools listed in 0.8s. Tool calls may still need a key. |
| maintenance | partial | 15 | Vendor-hosted rule: scored from vendor docs page 2026-10-01, date from page metadata (JSON-LD BlogPosting dateModified 2026-10-01T08:37:30.593Z (datePublished 2026-05-12T06:29:42.000Z), fetched 2026-11-11T08:34Z) (https://www.qt.io/blog/introducing-the-mcp-tool-for-qt-documentation), 41 days before test. Registry (corroboration only, not scored): io.qt.qt-docs-mcp/qt-documentation 0.4.0 published 2026-11-09. |
| docs | pass | 15 | official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://doc.qt.io/agentictools/mcp/setup-manual/). |
| license | fail | 0 | Vendor-hosted service with no public repo: no license to cite, so 0 (rule: no points without a cited source). |
Local-model readiness
Token cost (estimate): approx. 783 tokens, cl100k estimate for 2 tools · about 10% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-11
- We connected to the vendor's hosted endpoint with no credentials and asked for its tool list: it listed 2 tools (Method details: MCP
initializethentools/list) - Auth response: none. The endpoint answered without any login
- Vendor docs: official MCP docs page; states the endpoint URL; client setup instructions (15/15)
- Maintenance: dated vendor source, vendor docs page (date from page metadata) 2026-10-01 (15/25)
- License: a hosted service has no license to cite (0/10)
- Token cost (estimate)
Not tested
- Security: not audited (hosted service; no code to review, no permission or data-flow analysis)
- Behaviour after signing in, or with a real account
- Source code, repository activity or an open-source license (none published for the hosted service)
- Performance, rate limits or load
- Real tasks (no functional task runs yet)
Methodology: how we test (vendor-hosted rule). A high score means it responds and its vendor documents and dates it, not that giving it access to your data carries no risk.
Known security issues
Not checked (remote-only): hosted endpoint, version unknown.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-11 test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
794bb1243e08: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "qt-docs-remote",
"version": null,
"registry": "remote",
"status": "working",
"tested": "2026-11-11",
"tools_count": 2,
"deprecated": false,
"archived": null,
"tests": {
"install": [
"pass",
20,
"Endpoint https://qt-docs-mcp.qt.io/mcp reachable over streamable-http (HTTP 200) in 0.8s; no install step for remote servers."
],
"handshake": [
"pass",
30,
"MCP `initialize` (protocol 2025-11-25, server qt-docs-server 0.3.0) + `tools/list` over streamable-http succeeded with no credentials; 2 tools listed in 0.8s. Tool calls may still need a key."
],
"maintenance": [
"partial",
15,
"Vendor-hosted rule: scored from vendor docs page 2026-10-01, date from page metadata (JSON-LD BlogPosting dateModified 2026-10-01T08:37:30.593Z (datePublished 2026-05-12T06:29:42.000Z), fetched 2026-11-11T08:34Z) (https://www.qt.io/blog/introducing-the-mcp-tool-for-qt-documentation), 41 days before test. Registry (corroboration only, not scored): io.qt.qt-docs-mcp/qt-documentation 0.4.0 published 2026-11-09."
],
"docs": [
"pass",
15,
"official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://doc.qt.io/agentictools/mcp/setup-manual/)."
],
"license": [
"fail",
0,
"Vendor-hosted service with no public repo: no license to cite, so 0 (rule: no points without a cited source)."
]
}
}Install
https://qt-docs-mcp.qt.io/mcp
Tools listed
qt_documentation_read, qt_documentation_search
Tool history: captured Nov 11, 2026. All tool history.
Quick config
{
"mcpServers": {
"qt-documentation-mcp-remote": {
"type": "http",
"url": "https://qt-docs-mcp.qt.io/mcp"
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. No install step: it is a remote server at https://qt-docs-mcp.qt.io/mcp.
- Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (2 in our test).
{
"mcpServers": {
"qt-documentation-mcp-remote": {
"type": "http",
"url": "https://qt-docs-mcp.qt.io/mcp"
}
}
}Test history
- 2026-11-11: New
Related: Troubleshooting: Protocol version mismatch (HTTP 400)
FAQ
Is Qt Documentation MCP deprecated?
No. qt-docs-remote was not deprecated or archived when we last tested it on 2026-11-11.
What replaces Qt Documentation MCP?
Nothing; Qt Documentation MCP (official, remote) is not deprecated as of 2026-11-11.
Does Qt Documentation MCP need an API key?
No. It completed an MCP handshake with no credentials and listed 2 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.