Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.BetterDB-inc/monitor

NPM · @BETTERDB/MCP · SCANNED AUG 3

BetterDB MCP server - Valkey observability for Claude Code and other MCP clients

Available components

+32 this week 78 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. 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 5 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @betterdb/mcp

# add to Claude Code
claude mcp add betterdb-inc-monitor -- npx -y @betterdb/mcp
# add to Codex CLI
codex mcp add betterdb-inc-monitor -- npx -y @betterdb/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "betterdb-inc-monitor": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@betterdb/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add betterdb-inc-monitor --command npx --arg -y --arg @betterdb/mcp
# ~/.hermes/config.yaml
mcp_servers:
  betterdb-inc-monitor:
    command: "npx"
    args: ["-y", "@betterdb/mcp"]
// mcp.json
{
  "mcpServers": {
    "betterdb-inc-monitor": {
      "command": "npx",
      "args": [
        "-y",
        "@betterdb/mcp"
      ]
    }
  }
}
Changelog

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 Aug 26 +4
    • Stability: unverified → 0.27 functional
  • 2 Aug 26 +38
    • Install scripts: unverified → pass security
    • Provenance: unverified → pass security
    • Known CVEs: unverified → partial security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • The attested source repository moved: BetterDB-inc/monitor security
    • License: unverified → fail functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Schema quality: unverified → excellent functional
  • 1 Aug 26 +8
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 46

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Analysed npm/@betterdb/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

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:
https://slsa.dev/provenance/v1
Subject digest:
sha512:1835d39960d095b5bd0fe6f9e1e9b075c8a614ad232e396c72354162519d2a2e22e024e887f71f9a8a5bb116cc5f857480e1c28570b2dd0346b5dc868
Discovery method:
attestation_endpoint
Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 21 exposed · ~1,627 tokens

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.

Tool Tokens
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.

NameTypeReqDescription
endTimenumberEnd time (Unix timestamp ms)
instanceIdstringOptional instance ID override
limitnumberMax entries to return
reasonstringFilter by reason (auth, command, key, channel)
startTimenumberStart time (Unix timestamp ms)
usernamestringFilter 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.

NameTypeReqDescription
instanceIdstringOptional instance ID override
limitnumberMax events to return
metricTypestringFilter by metric type
startTimenumberStart 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.

NameTypeReqDescription
bucketSizeMinutesnumberBucket size in minutes (default 5)
endTimenumberEnd time (Unix timestamp ms)
instanceIdstringOptional instance ID override
startTimenumberStart time (Unix timestamp ms)

No output schema declared.

No examples provided.

get_clients ~29

Get the active client list with connection details.

NameTypeReqDescription
instanceIdstringOptional 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.

NameTypeReqDescription
instanceIdstringOptional 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.

NameTypeReqDescription
instanceIdstringOptional 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.

NameTypeReqDescription
instanceIdstringOptional instance ID override
limitnumberMax 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).

NameTypeReqDescription
countnumberNumber of entries to return (default 25)
instanceIdstringOptional 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.

NameTypeReqDescription
commandstringFilter by command name
endTimenumberEnd time (Unix timestamp ms)
instanceIdstringOptional instance ID override
limitnumberMax entries to return
minDurationnumberMin duration in microseconds
startTimenumberStart 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.

NameTypeReqDescription
endTimenumberEnd time (Unix timestamp ms)
instanceIdstringOptional instance ID override
limitnumberMax entries to analyze
startTimenumberStart 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.

NameTypeReqDescription
instanceIdstringOptional 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).

NameTypeReqDescription
endTimenumberEnd time (Unix timestamp ms)
instanceIdstringOptional instance ID override
limitnumberMax entries to return (default 50, max 200)
startTimenumberStart 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.

NameTypeReqDescription
instanceIdstringOptional instance ID override
sectionstringINFO 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.

NameTypeReqDescription
instanceIdstringOptional 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.

NameTypeReqDescription
eventNamestringyesLatency event name to query
instanceIdstringOptional instance ID override

No output schema declared.

No examples provided.

get_memory ~34

Get memory diagnostics: MEMORY DOCTOR assessment and MEMORY STATS breakdown.

NameTypeReqDescription
instanceIdstringOptional 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.

NameTypeReqDescription
instanceIdstringOptional instance ID override
limitnumberMax slots to return (default 20)
orderBystringSort 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.

NameTypeReqDescription
countnumberNumber of entries to return (default 25)
instanceIdstringOptional 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.

NameTypeReqDescription
instanceIdstringOptional instance ID override
limitnumberMax 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.

NameTypeReqDescription
instanceIdstringyesThe instance ID to select

No output schema declared.

No examples provided.