io.github.sijunkim/db-gateway

io.github.sijunkim/db-gatewayv1.0.2Databases

145+ tools across 8 databases: MySQL, PostgreSQL, Redshift, MongoDB, Redis, Kafka, and more

In-path gate · all MCP tools

Using io.github.sijunkim/db-gateway in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire

Auditable install path →Watch it hold a drift →

Trust verdict · v1 advisory · method

NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-08-07).

Contracts can change after screening, with no version bump. The gate pins io.github.sijunkim/db-gateway’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Environment variables

DBS

required

Engines to enable, comma-separated. Only the listed engines get their tools registered. Example: mysql,redis,kafka

READ_ONLY

Set to true to hide every write tool and restrict *_execute_query to SELECT-style statements. Recommended when pointing at production.

MYSQL

secret

MySQL connection string(s), semicolon-separated for multiple instances. Format: mysql://<user>:<password>@<host>:3306/<database>?alias=dev&default=true — alias is required.

POSTGRESQL

secret

PostgreSQL connection string(s), semicolon-separated. Format: postgresql://<user>:<password>@<host>:5432/<database>?alias=dev&ssl=true — alias is required.

REDSHIFT

secret

Redshift connection string(s), semicolon-separated. Format: redshift://<user>:<password>@<host>:5439/<database>?alias=dev&ssl=true — alias is required.

MONGODB

secret

MongoDB connection string(s), semicolon-separated. Format: mongodb://<user>:<password>@<host>:27017/<database>?alias=dev — alias is required.

REDIS

secret

Redis connection string(s), semicolon-separated. Format: redis://:<password>@<host>:6379/0?alias=dev — leave the password empty for a no-auth instance. alias is required.

ELASTICSEARCH

secret

Elasticsearch connection string(s), semicolon-separated. Format: elasticsearch://<user>:<password>@<host>:9200?alias=dev, or http(s)://<host>:9200?alias=dev for no auth. alias is required.

KAFKA

secret

Kafka connection string(s), semicolon-separated. Format: kafka://<user>:<password>@<broker1>:9092,<broker2>:9092?alias=dev&mechanism=plain — alias is required.

DYNAMODB_REGION

AWS region for DynamoDB. DynamoDB is configured with discrete variables instead of a connection string.

DYNAMODB_ACCESS_KEY_ID

secret

AWS access key ID for DynamoDB.

DYNAMODB_SECRET_ACCESS_KEY

secret

AWS secret access key for DynamoDB.

MCP quality score · maturity, not trust · methodology

freshness

completeness

installability

documentation

stability

Alternatives in Databases

Cortex RMCP

ai.dinglebear/cortex

Self-hosted homelab log intelligence over MCP, CLI, and REST with SQLite/FTS.

Aiven MCP

io.aiven/mcp

Provision PostgreSQL, manage Apache Kafka, and deploy apps with Aiven - all from your AI assistant.

io.github.smaniches/alphafold-sovereign-mcp

MCP server for AlphaFold and 8 other biomedical data sources with a local SQLite knowledge graph

Install this server

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "db-gateway": {
      "command": "npx",
      "args": [
        "-y",
        "--",
        "db-gateway"
      ],
      "env": {
        "DBS": "<dbs>",
        "READ_ONLY": "<read_only>",
        "MYSQL": "<your-mysql>",
        "POSTGRESQL": "<your-postgresql>",
        "REDSHIFT": "<your-redshift>",
        "MONGODB": "<your-mongodb>",
        "REDIS": "<your-redis>",
        "ELASTICSEARCH": "<your-elasticsearch>",
        "KAFKA": "<your-kafka>",
        "DYNAMODB_REGION": "<dynamodb_region>",
        "DYNAMODB_ACCESS_KEY_ID": "<your-dynamodb_access_key_id>",
        "DYNAMODB_SECRET_ACCESS_KEY": "<your-dynamodb_secret_access_key>"
      }
    }
  }
}

Cursor (.cursor/mcp.json)

{
  "mcpServers": {
    "db-gateway": {
      "command": "npx",
      "args": [
        "-y",
        "--",
        "db-gateway"
      ],
      "env": {
        "DBS": "<dbs>",
        "READ_ONLY": "<read_only>",
        "MYSQL": "<your-mysql>",
        "POSTGRESQL": "<your-postgresql>",
        "REDSHIFT": "<your-redshift>",
        "MONGODB": "<your-mongodb>",
        "REDIS": "<your-redis>",
        "ELASTICSEARCH": "<your-elasticsearch>",
        "KAFKA": "<your-kafka>",
        "DYNAMODB_REGION": "<dynamodb_region>",
        "DYNAMODB_ACCESS_KEY_ID": "<your-dynamodb_access_key_id>",
        "DYNAMODB_SECRET_ACCESS_KEY": "<your-dynamodb_secret_access_key>"
      }
    }
  }
}

Cline (cline_mcp_settings.json)

npx -y -- db-gateway

Claude Code (claude mcp add)

claude mcp add --scope user db-gateway -- npx -y -- db-gateway

Gemini CLI (gemini mcp add)

gemini mcp add -s user db-gateway npx -y -- db-gateway

Verdict API

curl -s mcpindex.ai/api/v1/trust/server/io-github-sijunkim-db-gateway

Free-tier verdict as JSON: decision + dimensions + severity. Call it from your agent before it invokes a tool it just discovered.

Details

version: v1.0.2
category: Databases
quality: 85 / 100
operator: sijunkim

Listing

Listed from the official MCP registry. Unclaimed by its maintainer. Maintainer? Email us →

Provenance

Each verdict is bound to a hash of the exact description it judged, so a re-crawl that changes the text produces a new record rather than silently inheriting this one. Verdict history is hash-chained and anchored to Bitcoin via OpenTimestamps (latest confirmed at block 961,250). Verify it yourself.

Links

Repository →