Home / MCP registry index / io.ddx.pg/archive
pg.ddx.io: the PostgreSQL community's memory
io.ddx.pg/archive in the official MCP registry.
Endpoint https://pg.ddx.io/mcp.
The registry describes it as: Every PostgreSQL mailing list since 1991, linked to the commits, code, commitfest and docs.
We read its 125 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
retrieve_context animal_history animal_owner_contributions blame_symbol browse_by_date build_status_freshness buildfarm_overview check_upstream_status code_index_status codebase_map commit_buildfarm_status commit_history commitfest_stats contribution_summary detect_changes discussion_links embedding_status entry_branches entry_history find_breaks find_contributions find_dead_code find_entries_for_author find_entries_for_thread find_entries_with_failures_on find_failing_patches find_failing_runs find_passing_long_pending find_patches_by_platform_status find_pattern find_rebase_needed_patches find_related_discussions find_similar_messages get_animal get_attachment get_author_messages get_callees get_callers get_commitfest get_communities get_community get_contributor get_contributor_history get_dependents get_doc_page get_entry get_execution_flows get_impact get_inbox_info get_inbox_stats get_inbox_summary get_message get_message_headers get_message_references get_new_messages get_patch_branches get_patch_build_history get_patch_series get_raw_message get_repo_sync_stats and 65 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-ddx-pg-archive)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
Postgres MCP servers · Memory and knowledge MCP servers
| io.sota/mcp io.sota/mcp | 14 tools, nothing matched 2026-10-21 |
| Veto — SQL Safety & Cost Oracle com.vetosql/veto | 3 tools, nothing matched 2026-10-21 |
| ai.getvda/kafka-and-postgres-monitoring-stack ai.getvda/kafka-and-postgres-monitoring-stack | 2 tools, nothing matched 2026-10-21 |
| ai.getvda/minio-postgres-redis-stack-generator ai.getvda/minio-postgres-redis-stack-generator | 2 tools, nothing matched 2026-10-21 |
| ai.getvda/postgres-grafana-stack-generator ai.getvda/postgres-grafana-stack-generator | 2 tools, nothing matched 2026-10-21 |
| ai.getvda/postgres-kafka-prometheus-stack-generator ai.getvda/postgres-kafka-prometheus-stack-generator | 2 tools, nothing matched 2026-10-21 |