C-

npm:@betterdb/mcp

https://www.npmjs.com/package/@betterdb/mcp
72/100 · MCP Trust Grade · checked 2h ago · MCP 1.2.0

What it offers — 30 tools · Developer Tools

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.

add_connection

Add a new Valkey/Redis connection to BetterDB. Optionally set it as the active default.

test_connection

Test a Valkey/Redis connection without persisting it. Use before add_connection to validate credentials.

remove_connection

Remove a connection from BetterDB.

set_default_connection

Set a connection as the active default for BetterDB.

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.

get_slowlog

Get the most recent slow commands from the slowlog.

get_commandlog

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

get_latency

Get latency event history for the active instance.

get_memory

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

get_clients

Get the active client list with connection details.

get_health

Get a synthetic health summary for the active instance: keyspace hit rate, memory fragmentation ratio, connected clients, replication lag (replicas on

get_slowlog_patterns

Get analyzed slowlog patterns from persisted storage. Groups slow commands by normalized pattern, showing frequency, average duration, and example com

get_commandlog_history

Get persisted COMMANDLOG entries from storage (Valkey 8+ only). Supports time range filtering to investigate specific incidents. Returns empty with a

get_commandlog_patterns

Get analyzed COMMANDLOG patterns from persisted storage (Valkey 8+ only). Like get_slowlog_patterns but includes large-request and large-reply pattern

get_anomalies

Get anomaly detection events from persisted storage. BetterDB continuously runs Z-score analysis on memory, hit rate, CPU, and other metrics — this re

get_client_activity

Get time-bucketed client activity from persisted snapshots. Shows connection counts, command distribution, and buffer usage over time. Use startTime/e

+12 more tools

Spec / packaging20%100
Security (OWASP MCP)30%25
Maintenance / popularity20%100
Tool hygiene15%95
Transparency / provenance15%65

Findings

WARNMCP08 References sensitive file paths / environment secrets.
INFO Static analysis of npm package @betterdb/mcp@1.2.0 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
Grade another server

We re-grade npm:@betterdb/mcp on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:@betterdb/mcp grade C-
Share on X Open card image

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

MCP Trust Grade C- · wmcp.sh
[![MCP Trust Grade C-](https://wmcp.sh/mcp/grade/npm%3A%40betterdb%2Fmcp/badge.svg)](https://wmcp.sh/mcp/grade/npm%3A%40betterdb%2Fmcp)
<a href="https://wmcp.sh/mcp/grade/npm%3A%40betterdb%2Fmcp"><img src="https://wmcp.sh/mcp/grade/npm%3A%40betterdb%2Fmcp/badge.svg" alt="MCP Trust Grade C- · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.