MQTT Specification
PYPI · MQTT-SPEC-MCP
Offline MCP server for navigating the OASIS MQTT 3.1.1 and 5.0 specifications
Available components
Last scanned (14 hours ago)
Scores higher than 57% of PyPI servers
Category IoT and Hardware
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs uv_build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to cartertinney/mqtt-spec-mcp). View diagnostics → Pass
- License check failed: the license (MIT AND LicenseRef-OASIS-Notices) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 479 tokens (~119/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 55% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 22 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 21 Oct 26 59
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 4 Nov 2026 · Analysed pypi/mqtt-spec-mcp@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | cartertinney/mqtt-spec-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/cartertinney/mqtt-spec-mcp/.github/workflows/release.yml@refs/tags/v0.1.0 |
| Rekor log index | 3359905514 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:57469d340f37b60eac8ff74622530f80f763eb9cc91b9f40d2dc848f6e79bfa3 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | uv_build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
mqtt_spec_get MQTT spec get section ~54
One section of one MQTT version as Markdown pages; continue a page with its Next cursor.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Next cursor. |
| section | string | yes | Section id or title. |
| version | string | yes | – |
No output schema declared.
No examples provided.
mqtt_spec_lookup MQTT spec lookup ~75
Exact entry for one packet, property or reason_code (5.0), return_code (3.1.1), requirement label or glossary term.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| packet | string | – | Packet filter. |
| query | string | yes | Exact name, number or label. |
| version | string | yes | – |
No output schema declared.
No examples provided.
mqtt_spec_outline MQTT spec outline ~37
Section ids and titles of one MQTT version, for browsing.
| Name | Type | Req | Description |
|---|---|---|---|
| parent | string | – | Section id. |
| version | string | yes | – |
No output schema declared.
No examples provided.
mqtt_spec_search MQTT spec search ~57
Evidence from one MQTT version: excerpts of the sections that best match the question.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The question's key terms; for several parts, one group per part, separated by ';'. |
| version | string | yes | – |
No output schema declared.
No examples provided.
How do I install the MQTT Specification MCP server?
MQTT Specification runs locally as a PyPI package, launched with uvx mqtt-spec-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mqtt-spec-mcp
claude mcp add cartertinney-mqtt-spec-mcp -- uvx mqtt-spec-mcp
What is the MQTT Specification MCP server?
MQTT Specification is an MCP server listed in the public MCP registry as io.github.cartertinney/mqtt-spec-mcp. Offline MCP server for navigating the OASIS MQTT 3.1.1 and 5.0 specifications. This page covers its PyPI package (mqtt-spec-mcp).
Is the MQTT Specification MCP server safe to use?
MQTT Specification scores 59 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 MQTT Specification MCP server expose?
MQTT Specification exposes 4 tools: mqtt_spec_outline, mqtt_spec_search, mqtt_spec_get, mqtt_spec_lookup. Their descriptions and schemas cost roughly 223 tokens of context every time the server is loaded.
Is the MQTT Specification MCP server still maintained?
MQTT Specification is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the MQTT Specification MCP server under?
MQTT Specification declares the MIT AND LicenseRef-OASIS-Notices licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.