mcp server
monitor
BetterDB MCP server - Valkey observability for Claude Code and other MCP clients
Description as published by the maintainer. Source
- version 0.1.4
- active
active — Most recent push to the repository was 2026-08-06.
What this server can do
21 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_acl_audit(limit, reason, endTime, username, startTime, instanceId)- 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(limit, startTime, instanceId, metricType)- 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(endTime, startTime, instanceId, bucketSizeMinutes)- 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(instanceId)- Get the active client list with connection details.
get_cluster_node_stats(instanceId)- 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(instanceId)- 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(limit, instanceId)- 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(count, instanceId)- Get the most recent entries from COMMANDLOG (Valkey 8+ only, superset of slowlog).
get_commandlog_history(limit, command, endTime, startTime, instanceId, minDuration)- 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(limit, endTime, startTime, instanceId)- 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(instanceId)- 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(limit, endTime, startTime, instanceId)- 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).
get_info(section, instanceId)- 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(instanceId)- Get latency event history for the active instance.
get_latency_history(eventName, instanceId)- 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. Required: eventName.
get_memory(instanceId)- Get memory diagnostics: MEMORY DOCTOR assessment and MEMORY STATS breakdown.
get_slot_stats(limit, orderBy, instanceId)- 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(count, instanceId)- Get the most recent slow commands from the slowlog.
get_slowlog_patterns(limit, instanceId)- 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(instanceId)- Select which instance subsequent tool calls operate on. Required: instanceId.
Last successful function declaration observed on
.
Source: pkg:npm/@betterdb/mcp. We list what the server declared;
we do not call any of these functions.
Endpoint status observed on
.
Source: pkg:npm/@betterdb/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 1,231 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-06 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 21 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.1.4 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-03-14 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-03-14 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub | |
| mcp tools declared | 21 tools | Number of functions the server declared when started and asked to list them. It says what the server offers an agent, not how well any of it works. | as of probe | npm |
|
| mcp endpoint status | ok | The server listed 21 functions when asked. | as of probe | npm |
|
| package install scripts | none | This package declares no install-time scripts, so installing it does not execute any of its code. | as of probe | npm |
Where to get it
Related, by what their authors tagged them
-
io.github.GeiserX/duplicacy-mcp
— last commit 2026-08-01, shares metrics, monitoring, prometheus
MCP server for Duplicacy — monitor backup status and Prometheus metrics
-
Steep
— last commit 2026-06-29, shares metrics
Query metrics, targets, entities, and team data in your Steep workspace via MCP.
-
Project Parva
— last commit 2026-08-05, shares redis
Read-only Nepali date, calendar, festival, Panchanga, and temporal verification tools.
-
MCP Toolbox for Databases
— last commit 2026-08-08, shares redis
MCP Toolbox for Databases enables your agent to connect to your database.
-
MCP Toolbox for Databases
— last commit 2026-08-08, shares redis
MCP Toolbox for Databases enables your agent to connect to your database.
-
World Monitor
— last commit 2026-08-06, shares monitoring
Live global intelligence: real-time markets, conflicts, country risk, chokepoints, energy. 39 tools.
-
com.clauxel.agentmonitorrelay/agentmonitorrelay-mcp
— last commit 2026-05-19, shares monitoring
AI agent run monitoring with incident replay and SLA receipts.
-
com.hyperping/hyperping
— last commit 2026-07-30, shares monitoring
Uptime, API and server monitoring with outages, reporting, on-call and status pages.
-
com.scoutapm/scout-mcp-local
— last commit 2026-06-20, shares monitoring
An MCP server for Scout Monitoring data interactions.
-
Monitoring AIops
— last commit 2026-08-03, shares monitoring
Governed SolarWinds Orion + PRTG + Zabbix ops: SWQL, alert rollup, health, 42 tools.
These share tags the maintainers applied themselves, such as metrics, monitoring, prometheus, redis. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: metrics, monitoring, obsevability, prometheus, redis, valkey.
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json