MQ-Sentinel
PYPI · MQ-SENTINEL
Read-only IBM MQ diagnostics for AI agents. Cited root cause, never destructive.
Available components
Last scanned (9 hours ago)
Scores higher than 29% of PyPI servers
Category Monitoring and Observability
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
- 3 of 61 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (Proprietary) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 15 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
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.
- 18 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 14 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 13 Oct 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.98 ▲ functional
- 12 Oct 26 −11
- Known CVEs: pass → unverified ▼ security
- Dependency health: 0.98 → unverified ▼ functional
- Package version: 0.3.0 → 0.5.0 functional
- 29 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 28 Sept 26 +15
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 25 Oct 2026 · Analysed pypi/mq-sentinel@0.5.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
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 61 packages
| Packages resolved | 61 |
|---|---|
| Stale | 3 |
| 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 →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the MQ-Sentinel MCP server?
MQ-Sentinel runs locally as a PyPI package, launched with uvx mq-sentinel. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mq-sentinel
claude mcp add pramodreddyboddu-mq-sentinel -- uvx mq-sentinel
What is the MQ-Sentinel MCP server?
MQ-Sentinel is an MCP server listed in the public MCP registry as io.github.pramodreddyboddu/mq-sentinel. Read-only IBM MQ diagnostics for AI agents. Cited root cause, never destructive. This page covers its PyPI package (mq-sentinel).
Is the MQ-Sentinel MCP server safe to use?
MQ-Sentinel scores 37 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 October 2026. 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.
Is the MQ-Sentinel MCP server still maintained?
MQ-Sentinel is still listed as active in the MCP registry. We last reached this channel on 25 October 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 MQ-Sentinel MCP server under?
MQ-Sentinel declares the Proprietary 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.