MQ-Sentinel
io.github.pramodreddyboddu由 GitHub 帳號 pramodreddyboddu 發布v0.5.0更新於 Oct 24, 2026
Read-only IBM MQ diagnostics for AI agents. Cited root cause, never destructive.
概覽
唯讀的 IBM MQ 診斷 MCP 伺服器,讓助理執行八項排障檢查並取得附引用的根因與修復步驟。
- 可以做什麼
- 診斷通道故障,包含授權與連線錯誤、INDOUBT 狀態及 AMQ 錯誤碼
- 依原因碼分析死信佇列並偵測重送回圈,僅讀取訊息標頭
- 檢查叢集健康、過期的叢集成員與異常的叢集通道
- 診斷 Native HA、RDQM 與多實例佇列管理員的副本延遲、仲裁與腦裂問題
- 檢查 z/OS 佇列共享群的 CHIN、分頁集與緩衝池
- 執行綜合健康檢查,回傳排序後的整體摘要
- 適用情境
- 適合執行 IBM MQ 的團隊,希望讓助理在不授予寫入權限的前提下排查通道故障、死信佇列、叢集、高可用或 z/OS 問題。主要面向需要可引用、可重現診斷結果的企業 MQ 維運與平台團隊。
- 執行需求
- 以 stdio 在本機執行,通常透過 uvx 從 PyPI 套件啟動。預設使用內建的示範佇列管理員;連線真實佇列管理員需要清單目錄、密鑰目錄,以及含 IBM MQ 用戶端函式庫的 pymqi 附加元件。生產環境可使用搭配 OIDC 的 HTTP 傳輸。環境變數包含 MQS_SERVER_ENVIRONMENT。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 MQ-Sentinel,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
MQ-Sentinel
Production-grade, read-only IBM MQ diagnostic MCP server that AI agents can safely use — with zero hallucinations.
I built this as a serious side project to solve a real, high-stakes problem in enterprise environments. It is now a strong public portfolio piece demonstrating systems engineering, security, observability, production deployment, and building safe infrastructure for AI agents.
[Python 3.12+] [mypy strict] [ruff] [tests 271 passing] [Org-Ready]
0.5.0 — 8 diagnostic tools across all 10 IBM MQ flavors. Read-only by design. Prompt-injection firewall. OIDC + RBAC. Hash-chained audit. Verified IBM Knowledge Center citations (CI-enforced). Production Helm with HPA + air-gapped packaging.
GitHub: https://github.com/pramodreddyboddu/mq-sentinel
Live Demo: https://mq-sentinel.io
Get it in front of people: docs/LAUNCH.md
The Problem I Solved
Enterprise IBM MQ teams waste hours diagnosing issues like:
- 2035 NOT_AUTHORIZED storms
- Exploding DLQs
- Native HA replica lag and split-brain
- Stale cluster members
- z/OS mysteries
Traditional tools require deep expertise and manual log diving. Handing an LLM raw MQ access is unacceptable for security and compliance teams.
MQ-Sentinel gives Claude, Cursor, Grok, and other agents a safe MCP interface that returns accurate, cited diagnostics without ever hallucinating or executing destructive commands.
The Problem
IBM MQ teams (banks, telcos, insurance, gov) waste hours on:
2035 NOT_AUTHORIZEDchannel storms- Exploding DLQs
- Native HA replica lag / split-brain
- Stale cluster members
- z/OS QSG mysteries
Traditional tools require deep MQSC knowledge and grepping logs. Giving an LLM direct MQ access is a non-starter for security/compliance teams.
MQ-Sentinel solves this by giving Claude, Cursor, Grok, etc. a safe, read-only MCP interface that returns typed Root Cause + Fix Steps + verified IBM docs — never fabricates, never executes destructive commands.
🎬 See it in 90 seconds
Watch MQ-Sentinel diagnose a real 2035 NOT_AUTHORIZED, an INDOUBT channel, a 1247-message DLQ, and a Native HA replica disconnect — all against the bundled fixture sandbox. No live IBM MQ required.
Want to record it for sharing?
make demo-recordproduces a browser-playable asciinema cast.
Quick self-check (no MQ needed):
Use it from Claude, Grok, Cursor, Gemini, ChatGPT
One MCP server — not a per-vendor plugin. Copy-paste configs: docs/mcp-clients.md.
List it where agents discover servers: official MCP Registry (server.json) + Smithery (smithery.yaml). ChatGPT needs a hosted HTTPS endpoint, not local stdio.
Architecture at a Glance
Safe by design. No LLM inside the server. Every citation verified in CI.
Why This Stands Out as a Portfolio Project
This is not a toy or weekend demo. It demonstrates real engineering depth:
- Systems + Security Engineering: Full threat model, multi-layer read-only enforcement, prompt-injection firewall, OIDC+RBAC, tamper-evident audit, hardened containers, SBOM + signed images.
- Production Operations: Production Helm (HPA, ServiceMonitor, NetworkPolicy), air-gapped packaging (RPM/DEB), observability out of the box.
- AI Agent Infrastructure: A complete, safe MCP server (stdio + HTTP) designed for real use by agents like Claude, Cursor, and Grok.
- Enterprise Domain Expertise: Deep coverage of IBM MQ across 10 topologies with version-aware, verified citations.
- Systematic Delivery: Executed a full 7-phase org-readiness plan with compliance artifacts that actual organizations need.
Built with Grok Build (primary coding partner) while maintaining strict engineering standards.
Full journey and plan: docs/ORG-READINESS-PLAN.md
See also: VISION.md · CONTRIBUTING.md · DEVELOPMENT.md
The Journey (Portfolio Story)
I built MQ-Sentinel to solve a painful, recurring problem in enterprise IBM MQ environments — and I treated the entire effort as a serious engineering and portfolio project.
I used Grok Build (xAI) as my primary coding partner from architecture through implementation, docs, Helm, compliance artifacts, and polish. Every major decision was deliberate: read-only first, citations that can't go stale, defense-in-depth, production packaging.
Key milestones:
- Designed threat model + multi-layer security architecture before writing the first tool
- Delivered 8 diagnostic tools across 10 MQ flavors with CI-enforced IBM Knowledge Center citations
- Production deployment (Helm + HPA + ServiceMonitor, distroless, air-gapped RPM/DEB)
- Full 7-phase org-readiness plan executed (see links above)
- 271+ tests (including security-negative tests), strict mypy, comprehensive docs for platform teams
This shows end-to-end ownership: deep domain knowledge, security by design, production operations, and shipping artifacts that real organizations can actually use.
This is my public portfolio project. It demonstrates systems engineering, security, observability, AI infrastructure, and disciplined delivery.
Built with Grok Build while holding high standards throughout.
Security posture — baked in, not bolted on
- Read-only always. Static MQSC allowlist (
DISPLAY/DIS/PING CHANNELonly). Destructive verbs are rejected by three layers: tool, connector, MQ-sidesetmqaut. - Prompt-injection firewall. Every MQ-sourced string is sanitized (control chars, zero-width, ANSI, unicode tag chars, jailbreak markers) and wrapped in a quarantine envelope before leaving the server.
- URL allowlist + live verification. Responses may only cite
www.ibm.com; all other URLs are redacted. Every citation in the registry (20+ reason codes, 8 AMQ codes, 18 topic pages) is fetched daily in CI — a dead link fails the build, not the customer. - Tamper-evident audit log. Hash-chained JSONL;
mq-sentinel verify-auditdetects any retroactive edit. - OIDC + RBAC. Principals scoped to
nonprod-read/prod-read/admin-audit. Cannot query prod QMs from a nonprod token. - Hardened runtime. Distroless image, non-root, read-only FS, dropped capabilities, seccomp, network egress allowlist.
- Supply chain. SBOM, cosign-signed images,
pip-audit+ Trivy in CI, every PR security-gated.
See SECURITY.md and docs/threat-model.md.
Org / Enterprise Ready?
This project was deliberately built for real organizations (banks, gov, large enterprises). See the complete journey:
See VISION.md for the owner product principles and long-term thinking.
- Org-Readiness Plan — 7-phase plan executed end-to-end
- Production Guide + Platform Team Onboarding
- Security Posture + SOC2 Evidence Checklist
- RBAC & Auth Examples (Okta, Entra ID, Keycloak)
- Production Helm with HPA, ServiceMonitor, network policies, and fleet support
- Observability — Grafana + Prometheus alerts ready to import
Skills & Engineering Rigor (Portfolio Highlights)
What this project demonstrates:
- Systems & Security Engineering — Full threat model, prompt-injection defense, multi-layer read-only enforcement, OIDC+RBAC, hash-chained audit, distroless hardening.
- Observability & Production Operations — Metrics, dashboards, alerts, runbooks, air-gapped packaging, Helm productionization.
- AI Agent Infrastructure — Built a real, safe MCP server (stdio + HTTP) that LLMs can use without risk.
- Enterprise Systems — Deep IBM MQ knowledge across 10 topologies + version-aware diagnostics.
- Software Craftsmanship — 271+ tests (including security), strict mypy, ruff, CI-driven doc verification, SBOM + cosign signing.
- End-to-End Delivery — From idea to org-ready artifacts, including comprehensive documentation that platform teams can actually use.
Built iteratively using Grok Build as the primary coding partner while maintaining high engineering standards.
Supported IBM MQ flavors (Phase 1 complete)
Standalone · Multi-Instance QM · RDQM · Native HA · Native HA + CRR · Uniform Cluster · Traditional Cluster · z/OS Queue Sharing Group · MQ Appliance · Containerized.
Diagnostic tools
Supported MQ versions
9.2 LTS, 9.3, 9.4 (incl. 9.4.4+), z/OS. Version is auto-detected at connect time; KC doc links are keyed to the detected version.
Install — pick your path
Full guide: docs/INSTALL.md. For IBM MQ client libs: docs/byom.md.
Connect real queue managers
Out of the box MQ-Sentinel serves the bundled demo QM (DEMO_QM). To diagnose your own QMs, set MQS_SERVER_INVENTORY_DIR (QM list) and MQS_SERVER_SECRETS_DIR (credentials), and install the mq extra (pymqi, which needs the IBM MQ client). The server then connects live over a display-only channel. docs/onboard-new-qm.md has the least-privilege setmqaut / CHLAUTH setup.
Quick start (developer / contributor)
See:
- DEVELOPMENT.md — owner-level development guide
- docs/usage-with-ai.md — best prompts and patterns when using with Claude / Cursor / Grok
- docs/ORG-READINESS-PLAN.md — the full journey to org-ready
Transports
See docs/http-transport.md for the OIDC config, endpoint reference, and operational notes.
Repository layout
Org-Readiness (7-Phase Plan Executed)
This project was deliberately taken through a complete org-readiness program (7 phases) so it is credible for real platform/SRE teams. See the full plan and status:
- docs/ORG-READINESS-PLAN.md
- docs/ORG-READINESS.md — all 7 phases addressed (as of 2026-06-22)
Current state: Ready for platform team evaluation.
Technical Roadmap
Phase 1 (MCP diagnostic tools) is complete. See CHANGELOG.md for future technical items:
- 0.4.0 — ServiceNow / Jira ticket auto-draft from RCS findings.
- 0.5.0 — SOC 2 evidence-pack generator.
- Historical telemetry, air-gapped improvements, etc.
Safe remediation is intentionally out of scope. MQ-Sentinel only reports.
For Organizations
MQ-Sentinel is designed from the ground up for enterprise use:
- Read-only, prompt-injection resistant, OIDC + RBAC
- Verifiable IBM Knowledge Center citations
- Production deployment options (Kubernetes, RPM/DEB, air-gapped)
- Full audit trail
Start here:
- Org Readiness Plan
- Production Guide
- Getting Started for Platform Teams
- OIDC Examples
- Security Posture
Helm chart includes production values, HPA, monitoring, and network policies.
License
Proprietary — © 2026 MG. See LICENSE. IBM® and IBM MQ® are trademarks of IBM Corporation; MG is not affiliated with IBM.
來源:README.md,提交 7cb2b2f
工具
0版本歷史
3- v0.5.0最新Oct 9, 2026
- v0.4.0Oct 9, 2026
- v0.3.0Sep 16, 2026
評分
已滿足適用檢查項的 40%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
請在儲存庫或註冊中心條目中宣告授權條款。