Qt Documentation MCP server
io.qt.qt-docs-mcp/qt-documentationqt-docs-mcp.qt.iostreamable-httpv0.4.0Scanned
Qt 5 and Qt 6 framework and product docs: Qt Creator, MCUs, Squish, Coco and more.
2 tools: 1 change things and 1 only read.
- Reads private data · 2
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Qt Documentation MCP server can do
The Qt Documentation MCP server is published by qt-docs-mcp.qt.io, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: qt_documentation_search), but cannot delete data. 1 tool only reads.
2 tools read private data (qt_documentation_read and qt_documentation_search).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 9, 2026, version 0.4.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 1Claude Code: ask
qt_documentation_searchCall 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)…Reads private data1 finding
Why it is in this group
- The name "qt_documentation_search" says "search": a word for reading.
- The description's first verb is "call": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- private-dataThe description's first sentence says "doc": it reads documents.
Findings
- Warn
The server marks "qt_documentation_search" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "qt_documentation_search" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
Only reads 1Show 1 read-only tool
qt_documentation_readRead the full content of a specific Qt documentation page, or a single member of it with 'symbol'.Reads private dataNo findings
Why it is in this group
- The name "qt_documentation_read" says "read": a word for reading.
What it can reach
- private-dataThe input names a file (input.file), and the tool reads: it reads files.
Description, as the server wrote it Read the full content of a specific Qt documentation page, or a single member of it with 'symbol'. Use the filename shown in search results.
Annotations the server declares
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:14 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-11-25
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://qt-docs-mcp.qt.io/mcp: tools/list returned 2 tools to an anonymous client, including qt_documentation_search (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "qt_documentation_search" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "qt_documentation_search" says "search": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:qt_documentation_readOnly readsdescriptioninputSchemaannotations
- Changed:qt_documentation_searchChanges thingsinputSchemaannotations
Install
Pinned to version 0.4.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http qt-documentation https://qt-docs-mcp.qt.io/mcpclaude mcp add --transport http qt-documentation https://qt-docs-mcp.qt.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__qt-documentation__qt_documentation_read"
],
"ask": [
"mcp__qt-documentation__qt_documentation_search"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as qt-documentation. Review it before you use it.
Capability tags behind 2 rules
- mcp__qt-documentation__qt_documentation_read private-data
- mcp__qt-documentation__qt_documentation_search private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.qt.qt-docs-mcp/qt-documentation/verify?hash=67e98ab3b8f7f71400c0cd640befb865e01bcf3dc8948f52728445f542736b90" | jq -e '.changed == false'Pinned hash 67e98ab3b8f7, from Nov 9, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.qt.qt-docs-mcp/qt-documentation/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.qt.qt-docs-mcp/qt-documentation)Source: MCP Registry. Synced Nov 9, 2026, 18:18 UTC.
Qt Documentation MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Qt Documentation MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Qt Documentation MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Qt Documentation MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Qt Documentation MCP server have?
- 2 tools: 1 write, 1 read. qt_documentation_search and qt_documentation_read.
Does the Qt Documentation MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Qt Documentation MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Qt Documentation MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 4, 2026. Every change is on this page and in its Atom feed.