
A hardened fork of CrystalDBA's postgres-mcp that routes all JSON-RPC traffic through an Ed25519-signed proxy layer. The Aegis Edge Proxy intercepts tool calls before they hit your database connection and mathematically blocks DROP, DELETE, and ALTER statements in under 2ms. You generate a capability token from the Aegis Cloud Console, run the Docker stack, and point your MCP client at localhost:8080 instead of directly at Postgres. The base server still exposes index tuning, EXPLAIN plans, schema intelligence, and health checks, but now every operation requires a valid X-Aegis-IBCT signature. Reach for this if you're running LLM database access in production and need SOC2 or HIPAA guardrails without trusting prompt engineering alone.
Public tool metadata for what this MCP can expose to an agent.
list_schemasLists all database schemas available in the PostgreSQL instance.Lists all database schemas available in the PostgreSQL instance.
No parameter schema in public metadata yet.
list_objectsLists database objects (tables, views, sequences, extensions) within a specified schema.Lists database objects (tables, views, sequences, extensions) within a specified schema.
No parameter schema in public metadata yet.
get_object_detailsProvides information about a specific database object, for example, a table's columns, constraints, and indexes.Provides information about a specific database object, for example, a table's columns, constraints, and indexes.
No parameter schema in public metadata yet.
execute_sqlExecutes SQL statements on the database, with read-only limitations when connected in restricted mode.Executes SQL statements on the database, with read-only limitations when connected in restricted mode.
No parameter schema in public metadata yet.
explain_queryGets the execution plan for a SQL query describing how PostgreSQL will process it and exposing the query planner's cost model. Can be invoked with hypothetical indexes to simulate the behavior after adding indexes.Gets the execution plan for a SQL query describing how PostgreSQL will process it and exposing the query planner's cost model. Can be invoked with hypothetical indexes to simulate the behavior after adding indexes.
No parameter schema in public metadata yet.
get_top_queriesReports the slowest SQL queries based on total execution time using `pg_stat_statements` data.Reports the slowest SQL queries based on total execution time using `pg_stat_statements` data.
No parameter schema in public metadata yet.
analyze_workload_indexesAnalyzes the database workload to identify resource-intensive queries, then recommends optimal indexes for them.Analyzes the database workload to identify resource-intensive queries, then recommends optimal indexes for them.
No parameter schema in public metadata yet.
analyze_query_indexesAnalyzes a list of specific SQL queries (up to 10) and recommends optimal indexes for them.Analyzes a list of specific SQL queries (up to 10) and recommends optimal indexes for them.
No parameter schema in public metadata yet.
analyze_db_healthPerforms comprehensive health checks including: buffer cache hit rates, connection health, constraint validation, index health (duplicate/unused/invalid), sequence limits, and vacuum health.Performs comprehensive health checks including: buffer cache hit rates, connection health, constraint validation, index health (duplicate/unused/invalid), sequence limits, and vacuum health.
No parameter schema in public metadata yet.
Sponsors