Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Qt Documentation

REMOTE · QT-DOCS-MCP.QT.IO · SCANNED AUG 3

Search Qt 6 API and product docs (Qt Core, Qt Quick, Qt Creator, Boot to Qt, MCUs).

+4 this week 62 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability51
  • AI-judged instruction clarity (good).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 Management27
  • Stability observed for 8 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · qt-docs-mcp.qt.io

# add to Claude Code
claude mcp add --transport http io-qt-qt-docs-mcp-qt-documentation https://qt-docs-mcp.qt.io/mcp
# ~/.codex/config.toml
[mcp_servers.io-qt-qt-docs-mcp-qt-documentation]
url = "https://qt-docs-mcp.qt.io/mcp"
// opencode.json
{
  "$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
    }
  }
}
# add to OpenClaw
openclaw mcp add io-qt-qt-docs-mcp-qt-documentation --url https://qt-docs-mcp.qt.io/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-qt-qt-docs-mcp-qt-documentation:
    url: "https://qt-docs-mcp.qt.io/mcp"
// mcp.json
{
  "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.

Changelog

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.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 +1
    • 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 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 +1
    • 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 57

    First indexed and scored.

Diagnostics

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 3 Aug 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=YE1,O=Let's Encrypt,C=US 20 Jul 2026 18 Oct 2026 ECDSA 256 ECDSA-SHA384 5d4cf9b155cd49c23a7ceb6f25ff326f616
SANs: qt-docs-mcp.qt.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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
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
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
MCP tools — 2 exposed · ~541 tokens

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.

Tool Tokens
qt_documentation_read ~119

Read the full content of a specific Qt documentation page. Use the filename shown in search results.

NameTypeReqDescription
filestringyesFilename 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.
versionstringOptional: 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.

NameTypeReqDescription
filterstringOptional: 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'.
intentstringOptional: Prioritizes (not filters) results by type. 'api'=class reference, 'tutorial'=how-to guides, 'guide'=overviews, 'concept'=explanations, 'example'=code samples, 'migration'=porting guides.
keywordsarrayOptional: Array of keywords to search for. Results match ANY keyword. Example: ["button", "signal", "connect"]. Alternative to 'query' for better multi-term matching.
max_resultsintegerOptional: Maximum number of results to return (1-10). Default is 3.
modulestringOptional: Limit search to specific Qt module (e.g., 'qtcore', 'qtwidgets', 'qtqml', 'qtquick', 'qtnetwork')
productstringOptional: Limit search to a specific documentation product (e.g. 'qt', 'qtcreator', 'pyside6'). Omit to search all products.
querystringSearch query for Qt documentation (e.g., 'Animation', 'QTimer', 'signal slot'). Optional if 'keywords' is provided.
versionstringOptional: 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.