PostgreSQL MCP server via psql subprocess
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"pg-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# pg-mcp PostgreSQL MCP server that executes queries via psql subprocess. No persistent connections — each query opens psql, runs SQL, closes. ## Config `~/.config/pg-mcp/connections.yml`: ```yaml connections: dev-mydb: host: db.example.com port: 5432 dbname: mydb user: myuser password: "mypassword" ``` ## Tools - `list_connections` — list configured connections - `list_tables(connection, schema?)` — list tables - `describe_table(connection, table, schema?)` — show columns and indexes - `query(connection, sql)` — execute SQL
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.