MCP.Market

Monitor MCP server

by BetterDB-inc·io.github.BetterDB-inc/monitor·v0.1.4·1.3k stars
No reviews yet

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

B82/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
Established

1.3k stars57 downloads/wk

Reviews

Write one

Nobody has reviewed Monitor yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Monitor tools (21)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • get_acl_audit

    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.

  • get_anomalies

    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.

  • get_client_activity

    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.

  • get_clients

    Get the active client list with connection details.

  • get_cluster_node_stats

    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.

  • get_cluster_nodes

    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.

  • get_cluster_slowlog

    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.

  • get_commandlog

    Get the most recent entries from COMMANDLOG (Valkey 8+ only, superset of slowlog).

  • get_commandlog_history

    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.

  • get_commandlog_patterns

    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.

  • get_health

    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.

  • get_hot_keys

    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 ind

  • get_info

    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.

  • get_latency

    Get latency event history for the active instance.

  • get_latency_history

    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.

  • get_memory

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

  • get_slot_stats

    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.

  • get_slowlog

    Get the most recent slow commands from the slowlog.

  • get_slowlog_patterns

    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.

  • list_instances

    List all Valkey/Redis instances registered in BetterDB. Shows connection status and capabilities.

  • select_instance

    Select which instance subsequent tool calls operate on.

Public scan report

scanner v0.1.10 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan3 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 2 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Monitor compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 63% of 48,255 servers
Tools
21
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1,302
more than 95% of 28,688 servers
Downloads a week
57
more than 47% of 12,191 servers with a package

What its tools let an agent do: 21 read

Install Monitor in Claude Code, Cursor or VS Code

Runs npx -y @betterdb/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add monitor -- npx -y @betterdb/mcp
Add to Cursor

What the publisher says

From the Monitor repository's README, as published. We do not edit it. Read it on GitHub

BetterDB Monitor

The monitoring layer that Valkey deserves.

BetterDB persists what Valkey throws away - slowlogs, command patterns, client activity, anomaly signals - so you can debug what happened at 3am, not just what's happening now. Built for Valkey 8.x with native support for COMMANDLOG, CLUSTER SLOT-STATS, and per-thread I/O metrics. Redis 6+ compatible for everything else.

Website | Docker Hub | npm | Documentation | Blog

BetterDB is built by BetterDB Inc., a public benefit company operating under the OCV Open Charter.

Quick Start (Docker)

docker run -d --name betterdb -p 3001:3001 betterdb/monitor:latest

Point your browser to http://localhost:3001. To monitor a specific instance:

docker run -d \
  --name betterdb \
  -p 3001:3001 \
  -e DB_HOST=your-valkey-host \
  -e DB_PORT=6379 \
  -e DB_PASSWORD=your-password \
  betterdb/monitor:latest

Connecting to a database on your host machine? Inside the container

localhost is the container itself, not your host — so use

host.docker.internal as the database host. On **Docker Desktop

(macOS/Windows) it works out of the box; on Linux** add

--add-host=host.docker.internal:host-gateway to the docker run command so

the name resolves. The dashboard's one-click "connect to local instance"

button auto-detects this and pre-fills the right host for you.

Two image variants are published, both multi-arch (linux/amd64, linux/arm64):

See Docker Production Deployment for persistent storage, custom ports, licensing, and air-gapped setups.

Quick Start (Kubernetes / Helm)

helm repo add betterdb https://docs.betterdb.com/charts
helm repo update
helm install betterdb-monitor betterdb/betterdb-monitor \
  --namespace betterdb --create-namespace \
  --set db.host=my-valkey.default.svc.cluster.local \
  --set db.password=yourpassword

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Monitor: common questions

Is Monitor MCP server safe?
Mostly: it is graded B (82/100). Read the Monitor safety report
How do I install Monitor?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Monitor need an API key?
Yes. The registry entry asks for BETTERDB_TOKEN.
Is Monitor maintained?
The last commit was 40 days ago (2026-09-25). The latest release is v0.1.4.
How does Monitor compare with other MCP servers?
safety score 82/100 (higher than 63% of 48,255 servers); tools 21 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.