io.github.daedalus/mcp-zmq
PYPI · MCP-ZMQ
MCP server for ZMQ messaging
Available components
Last scanned (3 hours ago)
Scores higher than 98% of PyPI servers
Category Communication
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 18 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency96
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to daedalus/mcp-zmq). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 213 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 565 tokens (~80/item across 7 items; 6 tools + 1 resources), lean.Pass
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "zmq_publish" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 7 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
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.
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −1
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.97 functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 −1
- Stability: pass → 0.93 functional
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 5 Nov 2026 · Analysed pypi/mcp-zmq@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 | daedalus/mcp-zmq |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/daedalus/mcp-zmq/.github/workflows/pypi-publish.yml@refs/tags/v0.1.0 |
| Rekor log index | 1239560676 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:8f7f8a551e2ca2b164036a1cc522081c5870e168929dffa98f94e3bef863f3f2 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 18 packages
| Packages resolved | 18 |
|---|---|
| Stale | 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 →
zmq_listen_reply Zmq Listen Reply ~89
Listen for requests and reply via ZMQ REP socket.
| Name | Type | Req | Description |
|---|---|---|---|
| bind_address | string | – | Address to bind REP socket. Defaults to "tcp://127.0.0.1:5556". |
| reply_message | string | – | Message to send in response to requests. Defaults to "OK". |
| timeout_ms | integer | – | Listen timeout in milliseconds. Defaults to 5000. |
Structured output declared, but exposes no named fields.
No examples provided.
zmq_pair_bind Zmq Pair Bind ~83
Bind a ZMQ PAIR socket for bi-directional communication.
| Name | Type | Req | Description |
|---|---|---|---|
| bind_address | string | – | Address to bind PAIR socket. Defaults to "tcp://127.0.0.1:5557". |
| message | string | – | Optional message to send after binding. |
| timeout_ms | integer | – | Timeout in milliseconds. Defaults to 5000. |
Structured output declared, but exposes no named fields.
No examples provided.
zmq_pair_connect Zmq Pair Connect ~84
Connect to a ZMQ PAIR socket for bi-directional communication.
| Name | Type | Req | Description |
|---|---|---|---|
| connect_address | string | – | Address to connect PAIR socket. Defaults to "tcp://127.0.0.1:5557". |
| message | string | – | Optional message to send after connecting. |
| timeout_ms | integer | – | Timeout in milliseconds. Defaults to 5000. |
Structured output declared, but exposes no named fields.
No examples provided.
zmq_publish Zmq Publish ~72
Publish a message to a ZMQ PUB socket.
| Name | Type | Req | Description |
|---|---|---|---|
| bind_address | string | – | Address to bind PUB socket. Defaults to "tcp://127.0.0.1:5555". |
| message | string | yes | Message payload to publish. |
| topic | string | yes | Message topic/topic filter for subscribers. |
Structured output declared, but exposes no named fields.
No examples provided.
zmq_send_request Zmq Send Request ~79
Send a request via ZMQ REQ socket.
| Name | Type | Req | Description |
|---|---|---|---|
| connect_address | string | – | Address to connect REQ socket. Defaults to "tcp://127.0.0.1:5556". |
| message | string | yes | Request payload to send. |
| timeout_ms | integer | – | Request timeout in milliseconds. Defaults to 5000. |
Structured output declared, but exposes no named fields.
No examples provided.
zmq_subscribe Zmq Subscribe ~87
Subscribe to messages from a ZMQ SUB socket.
| Name | Type | Req | Description |
|---|---|---|---|
| connect_address | string | – | Address to connect SUB socket. Defaults to "tcp://127.0.0.1:5555". |
| timeout_ms | integer | – | Receive timeout in milliseconds. Defaults to 5000. |
| topic_filter | string | – | Topic to subscribe to. Empty string subscribes to all topics. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.daedalus/mcp-zmq server?
io.github.daedalus/mcp-zmq runs locally as a PyPI package, launched with uvx mcp-zmq. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-zmq
claude mcp add daedalus-mcp-zmq -- uvx mcp-zmq
What is the io.github.daedalus/mcp-zmq server?
io.github.daedalus/mcp-zmq is listed in the public MCP registry as io.github.daedalus/mcp-zmq. MCP server for ZMQ messaging. This page covers its PyPI package (mcp-zmq).
Is the io.github.daedalus/mcp-zmq server safe to use?
io.github.daedalus/mcp-zmq scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 io.github.daedalus/mcp-zmq server expose?
io.github.daedalus/mcp-zmq exposes 6 tools: zmq_publish, zmq_subscribe, zmq_send_request, zmq_listen_reply, zmq_pair_connect, zmq_pair_bind. Their descriptions and schemas cost roughly 494 tokens of context every time the server is loaded.
Is the io.github.daedalus/mcp-zmq server still maintained?
io.github.daedalus/mcp-zmq is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.daedalus/mcp-zmq server under?
io.github.daedalus/mcp-zmq declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.