Databases

dbaas.dev

Provides tools to provision, manage, and query PostgreSQL databases, both ephemeral and persistent.

1 endpoint15 known toolsFirst detected May 29, 2026Last detected September 6, 2026

ENDPOINT 1

https://api.dbaas.dev/v1/mcp

No auth detected

MCP server metadata

Name: dbaas.dev
Version: 1.0.0

Capabilities

tools

Server instructions

Provision and manage PostgreSQL databases on dbaas.dev. Use provision_ephemeral_postgres for throwaway databases (no auth). Persistent database tools require an API key.

Known tools 15

provision_ephemeral_postgres

Provision a throwaway PostgreSQL database with a TTL of 1–60 minutes.

Inferred read-only

get_ephemeral_database

Poll an ephemeral database by id.

Inferred read-only

exec_sql_ephemeral

Execute SQL on an ephemeral database.

Potential side effects

list_databases

List persistent databases owned by the authenticated user.

Inferred read-only

create_database

Provision a new persistent PostgreSQL database.

Inferred read-only

get_database_info

Get connection details (host, port, username, connection string) for a persistent database.

Inferred read-only

exec_sql

Execute SQL on a persistent database.

Potential side effects

stop_database

Stop a running database (scales pod to 0; data preserved).

Inferred read-only

start_database

Start a stopped database.

Inferred read-only

delete_database

Permanently delete a database and its data.

Potential side effects

list_backups

List available backups for a database (newest first).

Inferred read-only

trigger_backup

Trigger an immediate pg_dump backup.

Inferred read-only

restore_backup

Restore a backup into the live database.

Inferred read-only

get_database_metrics

Get latest connection, memory, CPU, and storage metrics for a database.

Inferred read-only

describe_schema

List tables, indexes, views, and functions in a database.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.dbaas-dev]
url = "https://api.dbaas.dev/v1/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "dbaas-dev": {
      "type": "http",
      "url": "https://api.dbaas.dev/v1/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: dbaas-dev
Remote MCP URL: https://api.dbaas.dev/v1/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "dbaas-dev": {
      "url": "https://api.dbaas.dev/v1/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "dbaas-dev": {
      "type": "http",
      "url": "https://api.dbaas.dev/v1/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "dbaas-dev",
  "transport": "streamable-http",
  "url": "https://api.dbaas.dev/v1/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for dbaas.dev was fetched 2026-07-27T05:38:45.054Z and is being refreshed.

Trust status Trusted

dbaas.dev is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.