{"id":"pg-db-operation-mcp-server","name":"pg-db-operation-mcp-server","homepage":"https://pypi.org/project/pg-db-operation-mcp-server/","repo_url":null,"category":"infrastructure","subcategories":[],"tags":["postgres","mcp","database","sql","agent-integration"],"what_it_does":"An MCP server package intended to expose PostgreSQL database operations to an AI agent (pg “db operation” tooling) via the Model Context Protocol (MCP).","use_cases":["Allow an LLM/agent to run controlled SQL/DB operations against PostgreSQL using MCP tool calls","Build agent workflows that need read/write access to Postgres data (e.g., reporting, CRUD assistance, data backfills)","Integrate Postgres operations into an agent platform that supports MCP"],"not_for":["Untrusted agents performing arbitrary SQL without safety controls","Publicly exposed database access from the internet without network protections","Highly compliance-sensitive environments without explicit auditing, least-privilege DB credentials, and query allowlists"],"best_when":null,"avoid_when":null,"alternatives":["MCP servers that wrap Postgres with strict query allowlists","Direct Postgres access via application backend APIs (REST/GraphQL) with auditing","SQL agent frameworks that enforce parameterization and role-based permissions","Managed database tools (e.g., database administration consoles/APIs) rather than agent-driven SQL"],"af_score":31.5,"security_score":34.0,"reliability_score":22.5,"package_type":"mcp_server","discovery_source":["pypi"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:48:47.644620+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["PostgreSQL credentials (implied for DB access)"],"oauth":false,"scopes":false,"notes":"No README/package details were provided here about MCP-server authentication (e.g., whether the MCP server itself requires an API key). Auth appears likely to rely on database credentials, but this cannot be confirmed from the provided data."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information provided; likely self-hosted/open-source MCP server."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":31.5,"security_score":34.0,"reliability_score":22.5,"mcp_server_quality":45.0,"documentation_accuracy":30.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":45.0,"rate_limit_clarity":0.0,"tls_enforcement":40.0,"auth_strength":40.0,"scope_granularity":20.0,"dependency_hygiene":40.0,"secret_handling":30.0,"security_notes":"Because no repository/README content was provided, scores reflect uncertainty. For Postgres-integrating MCP servers, the main risks are overly-broad DB credentials, execution of arbitrary/destructive SQL, insufficient auditing, lack of TLS enforcement between MCP server and Postgres, and missing guardrails (query allowlists/parameterization).","uptime_documented":0.0,"version_stability":30.0,"breaking_changes_history":30.0,"error_recovery":30.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Agent-generated SQL can be destructive unless guarded (allowlists, read-only roles, transaction boundaries).","Without parameterization and strict input handling, the agent may produce unsafe queries.","If the MCP server exposes “execute SQL” style tools, agents may attempt multi-statement batches that are unsafe or unsupported.","DB connection errors/timeouts may require retry/backoff; guidance may not be documented."]}}