Betterdb MCP Server

@betterdb/mcp npm v1.5.0 Source verified

Published by betterdb-inc — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

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

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 94/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

high Shell/command execution in server code (dist/autostart.js)MTC-SRC-002

In the server's implementation (`dist/autostart.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: rt { spawn } from 'node:child_process'; import fs from 'node:fs'; import path from 'node:path'; import os from 'node:os'

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/autostart.js

Tools 60

Each tool and what it can reach — statically extracted from the published source.

  • cache_get_proposalingests untrusted input
  • memory_getingests untrusted input
  • add_connectionno sensitive capability
  • ai_instance_historyno sensitive capability
  • ai_list_instancesno sensitive capability
  • cache_approve_proposalno sensitive capability
  • cache_edit_and_approve_proposalno sensitive capability
  • cache_healthno sensitive capability
  • cache_listno sensitive capability
  • cache_list_pending_proposalsno sensitive capability
Show 50 more tools ↓
  • cache_propose_invalidateno sensitive capability
  • cache_propose_threshold_adjustno sensitive capability
  • cache_propose_tool_ttl_adjustno sensitive capability
  • cache_recent_changesno sensitive capability
  • cache_reject_proposalno sensitive capability
  • cache_similarity_distributionno sensitive capability
  • cache_threshold_recommendationno sensitive capability
  • cache_tool_effectivenessno sensitive capability
  • correlate_ai_traceno sensitive capability
  • get_acl_auditno sensitive capability
  • get_ai_traceno sensitive capability
  • get_anomaliesno sensitive capability
  • get_client_activityno sensitive capability
  • get_clientsno sensitive capability
  • get_cluster_node_statsno sensitive capability
  • get_cluster_nodesno sensitive capability
  • get_cluster_slowlogno sensitive capability
  • get_commandlogno sensitive capability
  • get_commandlog_historyno sensitive capability
  • get_commandlog_patternsno sensitive capability
  • get_forecastno sensitive capability
  • get_healthno sensitive capability
  • get_hot_keysno sensitive capability
  • get_inference_latencyno sensitive capability
  • get_infono sensitive capability
  • get_largest_keysno sensitive capability
  • get_latencyno sensitive capability
  • get_latency_historyno sensitive capability
  • get_latency_regressionsno sensitive capability
  • get_memoryno sensitive capability
  • get_slot_statsno sensitive capability
  • get_slowlogno sensitive capability
  • get_slowlog_patternsno sensitive capability
  • get_vector_indexesno sensitive capability
  • list_ai_tracesno sensitive capability
  • list_instancesno sensitive capability
  • memory_approve_forgetno sensitive capability
  • memory_forgetno sensitive capability
  • memory_listno sensitive capability
  • memory_list_pending_forgetsno sensitive capability
  • memory_recallno sensitive capability
  • memory_reject_forgetno sensitive capability
  • memory_statsno sensitive capability
  • memory_storesno sensitive capability
  • remove_connectionno sensitive capability
  • select_instanceno sensitive capability
  • set_default_connectionno sensitive capability
  • start_monitorno sensitive capability
  • stop_monitorno sensitive capability
  • test_connectionno sensitive capability

What this scan could not see

Versions 3

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.5.0 latest A 94/100 1 1.13.0 2026-09-07
v1.4.0 A 94/100 1 1.13.0 2026-08-31
v1.3.2 A 94/100 1 1.12.1 2026-07-28

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/betterdb-mcp/badge.svg)](https://mcptrustchecker.com/registry/betterdb-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/betterdb-mcp"><img src="https://mcptrustchecker.com/registry/betterdb-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/betterdb-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @betterdb/mcp --online

Use the free API → How scoring works

More in Databases