Multi Database MCP Server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Dated implementation activity and relevant MCP role justify continued Radar monitoring.

Reviewed Oct 9, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Operate multiple SQL databases through a self-hosted MCP server

What we know

Multi-database MCP supporting queries, transactions and schema/performance inspection with stdio, SSE and HTTP options.

Maintenance / activity evidence

GitHub REST repository pushed_at 2026-09-24T13:34:35Z for FreePeak/db-mcp-server

Tracking evidence observed Oct 9, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Execute SQL and transactions against configured databases Reported action classes: Execute SQL and transactions against configured databases. Complete write authority is not verified.
Database credentials; optional MCP bearer API key for HTTP/SSE
Sensitive access: Database credentials, Tables and records, Query results

Unauthenticated network transport possible unless DB_MCP_API_KEY or proxy is configured
Database access/write capabilities depend on connection credentials; require API key or protected reverse proxy before exposing HTTP transport.
Database queries can modify tables; read_only flag and row limit/masking guardrails are configurable, credentials carry DB privileges.
Unknown vulnerabilities and client-side tool approvals were not exhaustively evaluated.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

435 repository stars

Stars observed Oct 9, 2026.

Repository total for FreePeak/db-mcp-server.

All limitations / Review context

At the next review, has this exact implementation gained new releases, changed setup/security scope, or become suitable for Shortlist?

No verified blocker to PUBLIC RADAR TRACKING within the bounded first-party evidence reviewed; material permissions and mitigations are explicitly disclosed.

Unauthenticated network transport possible unless DB_MCP_API_KEY or proxy is configured
Database access/write capabilities depend on connection credentials; require API key or protected reverse proxy before exposing HTTP transport.
Database queries can modify tables; read_only flag and row limit/masking guardrails are configurable, credentials carry DB privileges.
Execute SQL and transactions against configured databases
Database credentials; optional MCP bearer API key for HTTP/SSE
Depends on configured local process, connected account and remote APIs; review first-party privacy terms for any hosted component.
Reviewed write actions: Execute SQL and transactions against configured databases
Sensitive access: Database credentials, Tables and records, Query results
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Unknown vulnerabilities and client-side tool approvals were not exhaustively evaluated.
production authorization and network isolation depend on deployment
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
SQL access can mutate/drop data
HTTP/SSE authentication is optional, not enabled by default
Protect network exposure
No independent release lifecycle audit; do not claim precise activity date.

Original activity observations

GitHub REST repository pushed_at 2026-09-24T13:34:35Z for FreePeak/db-mcp-server

Technical identity

github.com/FreePeak/db-mcp-server

Exact implementation source: https://github.com/FreePeak/db-mcp-server ↗
Reviewed resource type: MCP Server
Repository identity: FreePeak/db-mcp-server

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 9, 2026 · Latest source observation Oct 9, 2026

GitHub repository ↗
freepeak/db-mcp-server
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 12, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Use the publisher-documented command or connection method below; complete the prerequisites and client configuration before expecting a usable MCP connection.
git clone https://github.com/FreePeak/db-mcp-server.git cd db-mcp-server make build ./bin/server -t stdio -c config.json
Configure / authenticate
Publisher instructions
Create a configuration JSON using the publisher-defined schema_version/connections shape. Prefer password_env to inline database passwords, configure valid database host/path and choose read_only=true with minimum database privileges. Run the compiled server only with the matching -c config path; its bundled example may default to read_only=false.
Check connection
Suggested check
Start with a disposable database, check startup connection logs or the publisher health_<db_id> tool and inspect connectivity/pool status. The db_health performance action may be available for configured databases; do not use execute/transaction/write operations for smoke tests. The action name depends on a configured database; never use a generic unverified shell health command.
Remove / uninstall / revoke
For a Cursor registration named `stdio-db-mcp-server`, remove only that entry from `.cursor/mcp.json` and restart Cursor. Stop the `./bin/server` process or matching Docker container independently. Do not remove database volumes.

Official Documentation & Sources

What it does

Multi-database MCP supporting queries, transactions and schema/performance inspection with stdio, SSE and HTTP options.

Capability: Data & Databases
Resource type: MCP Server
Best fit: Operate multiple SQL databases through a self-hosted MCP server

Representative uses

Query multiple databases
Inspect schemas
Execute transactions
Diagnose slow queries

Limitations

SQL access can mutate/drop data
HTTP/SSE authentication is optional, not enabled by default
Protect network exposure
Unauthenticated network transport possible unless DB_MCP_API_KEY or proxy is configured
No independent release lifecycle audit; do not claim precise activity date.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Database credentials; optional MCP bearer API key for HTTP/SSE
Permissions: Execute SQL and transactions against configured databases
Data handling: Depends on configured local process, connected account and remote APIs; review first-party privacy terms for any hosted component.
Cost: unknown
Risk and cautions: Unauthenticated network transport possible unless DB_MCP_API_KEY or proxy is configured

Access scope and cautions

Write actions: Not verified Execute SQL and transactions against configured databases
Sensitive access: Database credentials Tables and records Query results
Risk level: high
Security notes: Database access/write capabilities depend on connection credentials; require API key or protected reverse proxy before exposing HTTP transport. Database queries can modify tables; read_only flag and row limit/masking guardrails are configurable, credentials carry DB privileges.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Query multiple databases; Inspect schemas; Execute transactions; Diagnose slow queries.

What setup and authentication are documented?

A complete connection procedure is not verified. Recorded transport: stdio, sse, streamable_http. Client notes: Source docs and package may evolve; install according to confirmed release. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Database credentials; optional MCP bearer API key for HTTP/SSE

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Execute SQL and transactions against configured databases. Recorded permission context: Execute SQL and transactions against configured databases

What data-handling boundary should I consider?

Depends on configured local process, connected account and remote APIs; review first-party privacy terms for any hosted component. Recorded sensitive-access context: Database credentials; Tables and records; Query results.

What limitations and risks should I check before use?

Unauthenticated network transport possible unless DB_MCP_API_KEY or proxy is configured. SQL access can mutate/drop data. HTTP/SSE authentication is optional, not enabled by default. Protect network exposure. No independent release lifecycle audit; do not claim precise activity date. Database access/write capabilities depend on connection credentials; require API key or protected reverse proxy before exposing HTTP transport. Database queries can modify tables; read_only flag and row limit/masking guardrails are configurable, credentials carry DB privileges. Unknown vulnerabilities and client-side tool approvals were not exhaustively evaluated.