{"id":"swanhtetaungphyo-postgres-mcp-server","name":"postgres-mcp-server","af_score":38.0,"security_score":44.5,"reliability_score":16.2,"what_it_does":"Provides an MCP (Model Context Protocol) server that enables an AI assistant to interact with a PostgreSQL database using three tools: execute_query (SELECT/read), ddl_query (schema changes), and modify_query (INSERT/UPDATE/DELETE). The README claims queries are validated and restricted to block dangerous operations (e.g., DROP/administrative commands) before execution.","best_when":"You run the MCP server in a trusted environment (e.g., local/dev or tightly controlled backend) and use database credentials with least privilege to limit what the assistant can do.","avoid_when":"When you cannot enforce network/trust boundaries or cannot ensure the database user has least-privilege permissions, since the assistant may still be able to execute allowed statements that impact data.","last_evaluated":"2026-04-04T21:21:02.628665+00:00","has_mcp":true,"has_api":false,"auth_methods":[],"has_free_tier":false,"known_gotchas":["The server does not automatically LIMIT results; agents should include LIMIT to avoid huge result sets and timeouts.","Tool routing matters: SELECT queries go to execute_query; schema changes go to ddl_query; data modifications go to modify_query.","Validation/rules are described at a high level in README; exact allow/deny behavior may differ, so agents may need to iteratively adapt to rejected queries."],"error_quality":0.0}