io.github.BetterDB-inc/monitor
NPM · @BETTERDB/MCP
BetterDB MCP server - Valkey observability for Claude Code and other MCP clients
Available components
Last scanned (19 hours ago)
Scores higher than 91% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 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 BetterDB-inc/monitor). View diagnostics → Pass
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 64 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1627 tokens (~77/item across 21 items; 21 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 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 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.
- 4 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.93 functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 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/@betterdb/mcp@0.1.3
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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | BetterDB-inc/monitor |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/BetterDB-inc/monitor/.github/workflows/mcp-release.yml@refs/tags/mcp-v0.1.3 |
| Rekor log index | 1097275022 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:1835d39960d095b5bd0fe6f9e1e9b075c8a614ad232e396c72354162519d2a2e22e024e887f71f9a8a5bb116cc5f857480e1c28570b2dd0346b5dc868 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
get_acl_audit ~130
Get persisted ACL audit log entries from storage. Filter by username, reason (auth, command, key, channel), or time range. Use this to investigate why a connection is failing or audit access patterns.
| Name | Type | Req | Description |
|---|---|---|---|
| endTime | number | – | End time (Unix timestamp ms) |
| instanceId | string | – | Optional instance ID override |
| limit | number | – | Max entries to return |
| reason | string | – | Filter by reason (auth, command, key, channel) |
| startTime | number | – | Start time (Unix timestamp ms) |
| username | string | – | Filter by username |
No output schema declared.
No examples provided.
get_anomalies ~105
Get anomaly detection events from persisted storage. BetterDB continuously runs Z-score analysis on memory, hit rate, CPU, and other metrics — this returns the detected anomalies. Use to investigate what triggered an alert or correlate with an incident.
| Name | Type | Req | Description |
|---|---|---|---|
| instanceId | string | – | Optional instance ID override |
| limit | number | – | Max events to return |
| metricType | string | – | Filter by metric type |
| startTime | number | – | Start time (Unix timestamp ms) |
No output schema declared.
No examples provided.
get_client_activity ~103
Get time-bucketed client activity from persisted snapshots. Shows connection counts, command distribution, and buffer usage over time. Use startTime/endTime to focus on a specific incident window.
| Name | Type | Req | Description |
|---|---|---|---|
| bucketSizeMinutes | number | – | Bucket size in minutes (default 5) |
| endTime | number | – | End time (Unix timestamp ms) |
| instanceId | string | – | Optional instance ID override |
| startTime | number | – | Start time (Unix timestamp ms) |
No output schema declared.
No examples provided.
get_clients ~29
Get the active client list with connection details.
| Name | Type | Req | Description |
|---|---|---|---|
| instanceId | string | – | Optional instance ID override |
No output schema declared.
No examples provided.
get_cluster_node_stats ~59
Get per-node performance stats: memory usage, ops/sec, connected clients, replication offset, and CPU. Use this to identify hot nodes, lagging replicas, or uneven load distribution.
| Name | Type | Req | Description |
|---|---|---|---|
| instanceId | string | – | Optional instance ID override |
No output schema declared.
No examples provided.
get_cluster_nodes ~60
Discover all nodes in the Valkey cluster — role (master/replica), address, health status, and slot ranges. Returns an error message if this instance is not running in cluster mode.
| Name | Type | Req | Description |
|---|---|---|---|
| instanceId | string | – | Optional instance ID override |
No output schema declared.
No examples provided.
get_cluster_slowlog ~80
Get the aggregated slowlog across ALL nodes in the cluster. This is the primary tool for finding slow commands in cluster mode — per-node slowlogs are incomplete. Returns an error message if not in cluster mode.
| Name | Type | Req | Description |
|---|---|---|---|
| instanceId | string | – | Optional instance ID override |
| limit | number | – | Max entries to return (default 100) |
No output schema declared.
No examples provided.
get_commandlog ~59
Get the most recent entries from COMMANDLOG (Valkey 8+ only, superset of slowlog).
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of entries to return (default 25) |
| instanceId | string | – | Optional instance ID override |
No output schema declared.
No examples provided.
get_commandlog_history ~124
Get persisted COMMANDLOG entries from storage (Valkey 8+ only). Supports time range filtering to investigate specific incidents. Returns empty with a note if COMMANDLOG is not supported on this instance.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | – | Filter by command name |
| endTime | number | – | End time (Unix timestamp ms) |
| instanceId | string | – | Optional instance ID override |
| limit | number | – | Max entries to return |
| minDuration | number | – | Min duration in microseconds |
| startTime | number | – | Start time (Unix timestamp ms) |
No output schema declared.
No examples provided.
get_commandlog_patterns ~98
Get analyzed COMMANDLOG patterns from persisted storage (Valkey 8+ only). Like get_slowlog_patterns but includes large-request and large-reply patterns in addition to slow commands.
| Name | Type | Req | Description |
|---|---|---|---|
| endTime | number | – | End time (Unix timestamp ms) |
| instanceId | string | – | Optional instance ID override |
| limit | number | – | Max entries to analyze |
| startTime | number | – | Start time (Unix timestamp ms) |
No output schema declared.
No examples provided.
get_health ~80
Get a synthetic health summary for the active instance: keyspace hit rate, memory fragmentation ratio, connected clients, replication lag (replicas only), and keyspace size. Use this as the first call when investigating an instance — it surfaces the most actionable signals without requiring you to parse raw INFO output.
| Name | Type | Req | Description |
|---|---|---|---|
| instanceId | string | – | Optional instance ID override |
No output schema declared.
No examples provided.
get_hot_keys ~160
Get hot key tracking data from persisted storage. BetterDB periodically scans keys using LFU frequency scores (when maxmemory-policy is an LFU variant) or OBJECT IDLETIME / COMMANDLOG-derived frequency. Each snapshot captures the top keys ranked by access frequency. Use this to find cache-busting keys, uneven access patterns, or keys that dominate throughput. The signalType field in each entry indicates which detection mode was active (lfu or idletime).
| Name | Type | Req | Description |
|---|---|---|---|
| endTime | number | – | End time (Unix timestamp ms) |
| instanceId | string | – | Optional instance ID override |
| limit | number | – | Max entries to return (default 50, max 200) |
| startTime | number | – | Start time (Unix timestamp ms) |
No output schema declared.
No examples provided.
get_info ~99
Get INFO stats for the active instance. Contains all health data: memory, clients, replication, keyspace, stats (hit rate, ops/sec), and server info. Optionally filter to a section: server|clients|memory|stats|replication|keyspace.
| Name | Type | Req | Description |
|---|---|---|---|
| instanceId | string | – | Optional instance ID override |
| section | string | – | INFO section to filter (server, clients, memory, stats, replication, keyspace) |
No output schema declared.
No examples provided.
get_latency ~29
Get latency event history for the active instance.
| Name | Type | Req | Description |
|---|---|---|---|
| instanceId | string | – | Optional instance ID override |
No output schema declared.
No examples provided.
get_latency_history ~80
Get the full latency history for a named event (e.g. 'command', 'fast-command'). Call get_latency first to see which event names are available, then use this to investigate a specific event's trend over time.
| Name | Type | Req | Description |
|---|---|---|---|
| eventName | string | yes | Latency event name to query |
| instanceId | string | – | Optional instance ID override |
No output schema declared.
No examples provided.
get_memory ~34
Get memory diagnostics: MEMORY DOCTOR assessment and MEMORY STATS breakdown.
| Name | Type | Req | Description |
|---|---|---|---|
| instanceId | string | – | Optional instance ID override |
No output schema declared.
No examples provided.
get_slot_stats ~113
Get per-slot key counts and CPU usage (Valkey 8.0+ only). Use orderBy='cpu-usec' to find hot slots, or 'key-count' to find the most populated slots. Returns an error message if not supported.
| Name | Type | Req | Description |
|---|---|---|---|
| instanceId | string | – | Optional instance ID override |
| limit | number | – | Max slots to return (default 20) |
| orderBy | string | – | Sort order: 'key-count' or 'cpu-usec' (default 'key-count') |
No output schema declared.
No examples provided.
get_slowlog ~49
Get the most recent slow commands from the slowlog.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of entries to return (default 25) |
| instanceId | string | – | Optional instance ID override |
No output schema declared.
No examples provided.
get_slowlog_patterns ~80
Get analyzed slowlog patterns from persisted storage. Groups slow commands by normalized pattern, showing frequency, average duration, and example commands. Survives slowlog buffer rotation — data goes back as far as BetterDB has been running.
| Name | Type | Req | Description |
|---|---|---|---|
| instanceId | string | – | Optional instance ID override |
| limit | number | – | Max entries to analyze |
No output schema declared.
No examples provided.
list_instances ~26
List all Valkey/Redis instances registered in BetterDB. Shows connection status and capabilities.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
select_instance ~30
Select which instance subsequent tool calls operate on.
| Name | Type | Req | Description |
|---|---|---|---|
| instanceId | string | yes | The instance ID to select |
No output schema declared.
No examples provided.
How do I install the io.github.BetterDB-inc/monitor MCP server?
io.github.BetterDB-inc/monitor runs locally as an npm package, launched with npx -y @betterdb/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 · @betterdb/mcp
claude mcp add betterdb-inc-monitor -- npx -y @betterdb/mcp
What is the io.github.BetterDB-inc/monitor MCP server?
io.github.BetterDB-inc/monitor is an MCP server listed in the public MCP registry as io.github.BetterDB-inc/monitor. BetterDB MCP server - Valkey observability for Claude Code and other MCP clients. This page covers its npm package (@betterdb/mcp).
Is the io.github.BetterDB-inc/monitor MCP server safe to use?
io.github.BetterDB-inc/monitor scores 87 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. 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.BetterDB-inc/monitor MCP server expose?
io.github.BetterDB-inc/monitor exposes 21 tools: list_instances, select_instance, get_info, get_slowlog, get_commandlog, and 16 more. Their descriptions and schemas cost roughly 1,627 tokens of context every time the server is loaded.
Is the io.github.BetterDB-inc/monitor MCP server still maintained?
io.github.BetterDB-inc/monitor 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.