io.github.Musaraf-M/sentinal-mcp
NPM · @MD-MUSARAF/SENTINAL-MCP
Redis health, BullMQ queue monitoring, memory analysis, and slow query diagnostics
Available components
Last scanned (23 hours ago)
Scores higher than 87% of npm 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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 35 of 99 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 182 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 415 tokens (~51/item across 8 items; 8 tools + 0 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.97 functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- 19 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
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 npm/@md-musaraf/sentinal-mcp@1.0.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 99 packages
| Packages resolved | 99 |
|---|---|
| Stale | 35 |
| 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 →
bullmq_failed_jobs ~69
Inspect failed jobs in a BullMQ queue — shows job ID, name, error reason, attempts, and stack trace
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of failed jobs to return |
| queue | string | yes | BullMQ queue name |
| redis_url | string | – | Redis connection URL |
No output schema declared.
No examples provided.
bullmq_job_details ~63
Get full details of a specific BullMQ job — payload, status, timestamps, error info
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Job ID to inspect |
| queue | string | yes | BullMQ queue name |
| redis_url | string | – | Redis connection URL |
No output schema declared.
No examples provided.
bullmq_list ~41
List all BullMQ queues with job counts per state (waiting, active, delayed, failed, completed)
| Name | Type | Req | Description |
|---|---|---|---|
| redis_url | string | – | Redis connection URL |
No output schema declared.
No examples provided.
bullmq_stale_jobs ~69
Find stale active jobs in a BullMQ queue — jobs stuck in active state longer than expected
| Name | Type | Req | Description |
|---|---|---|---|
| minutes | number | – | Consider jobs stale if active longer than this many minutes |
| queue | string | yes | BullMQ queue name |
| redis_url | string | – | Redis connection URL |
No output schema declared.
No examples provided.
redis_health ~40
Comprehensive Redis health report — server info, memory, clients, slow queries, and BullMQ queue depths
| Name | Type | Req | Description |
|---|---|---|---|
| redis_url | string | – | Redis connection URL |
No output schema declared.
No examples provided.
redis_memory ~58
Analyze Redis memory usage — used, peak, fragmentation, big keys, and memory doctor recommendations
| Name | Type | Req | Description |
|---|---|---|---|
| big_keys | boolean | – | Run big keys scan (takes longer but finds memory hogs) |
| redis_url | string | – | Redis connection URL |
No output schema declared.
No examples provided.
redis_ping ~26
Test connectivity to a Redis instance
| Name | Type | Req | Description |
|---|---|---|---|
| redis_url | string | – | Redis connection URL |
No output schema declared.
No examples provided.
redis_slowlog ~49
Show Redis slow queries — find commands that took too long to execute
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of slow log entries to return |
| redis_url | string | – | Redis connection URL |
No output schema declared.
No examples provided.
How do I install the io.github.Musaraf-M/sentinal-mcp server?
io.github.Musaraf-M/sentinal-mcp runs locally as an npm package, launched with npx -y @md-musaraf/sentinal-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @md-musaraf/sentinal-mcp
claude mcp add musaraf-m-sentinal-mcp -- npx -y @md-musaraf/sentinal-mcp
What is the io.github.Musaraf-M/sentinal-mcp server?
io.github.Musaraf-M/sentinal-mcp is listed in the public MCP registry as io.github.Musaraf-M/sentinal-mcp. Redis health, BullMQ queue monitoring, memory analysis, and slow query diagnostics. This page covers its npm package (@md-musaraf/sentinal-mcp).
Is the io.github.Musaraf-M/sentinal-mcp server safe to use?
io.github.Musaraf-M/sentinal-mcp scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. 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.Musaraf-M/sentinal-mcp server expose?
io.github.Musaraf-M/sentinal-mcp exposes 8 tools: redis_ping, redis_health, redis_memory, redis_slowlog, bullmq_list, and 3 more. Their descriptions and schemas cost roughly 415 tokens of context every time the server is loaded.
Is the io.github.Musaraf-M/sentinal-mcp server still maintained?
io.github.Musaraf-M/sentinal-mcp 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 io.github.Musaraf-M/sentinal-mcp server under?
io.github.Musaraf-M/sentinal-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.