io.github.cocaxcode/database-mcp

Name: io.github.cocaxcode/database-mcp
Rating: 60 (1 reviews)
Author: io.github.cocaxcode

MCPcommunity

v0.1.14io.github.cocaxcodeUnknownUpdated 3mo agonpm GitHub

MCP server for database connectivity. Multi-DB (PostgreSQL, MySQL, SQLite), 19 tools.

@cocaxcode/database-mcp Your databases, one conversation away. 33 tools · PostgreSQL · MySQL · SQLite · Connection Groups · Rollback · Dump/Restore · Schema auto-discovery Just Talk to It · Connection Groups · Installation · Tool Reference · The most complete MCP server for databases. 33 tools across 3 engines…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

3mo agoLast update

Package

Authorio.github.cocaxcode

LicenseUnknown

Version0.1.14

Sourcemcp-registry

npm@cocaxcode/database-mcp

GitHubcocaxcode/database-mcp

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/25

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/10

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

—npm provenance (Sigstore)+0/5

→ Publish from GitHub Actions with the --provenance flag

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface34 tools · 5 privileged

Security scan✓ Cleanv0.3.4 · 20d ago

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Keywords

mcp