Is the pg.ddx.io: the PostgreSQL community's memory MCP server down?

mcp-registry/io.ddx.pg/archive · registry v2026.10.22 · server reports v1.0

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 17:06 UTC · handshake 313ms

As of 2026-11-22 17:06 UTC, the pg.ddx.io: the PostgreSQL community's memory MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 4 minutes.

uptime (30d checks)
99.9%
checks observed
897
outages (90d)
2
tools
130

Every PostgreSQL mailing list since 1991, linked to the commits, code, commitfest and docs.

Point your MCP client at this streamable-http endpoint: https://pg.ddx.io/mcp

Agent-readiness: B (83/100)

B (83/100): 0 error(s), 2 warning(s) across 130 tool(s); ~16,137 tokens of tool definitions.
Scores higher than 32% of 27,662 MCP servers Glimind has audited.
Its tool list costs an agent ~16,137 tokens per session — more than 85% of servers.
90 → 83 since 2026-11-16
no tool-poisoning patterns
Descriptions55
Safety hints100
Schemas100
Protocol100
Stability20
Token cost75
Reliability100
Client compatibility100

What to fix (3)

130 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

83 parameter(s) across 65 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: blame, blame_symbol, code_index_status, codebase_map, combine_calendars and 60 more

In the last 30 days: 0 tool(s) removed and 214 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.ddx.pg/archive"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.ddx.pg/archive"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fio.ddx.pg%2Farchive.svg)](https://glimind.com/server/mcp-registry%2Fio.ddx.pg%2Farchive?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.ddx.pg%2Farchive?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.ddx.pg%2Farchive.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:befe29c6d206c651…, first seen 2026-11-20, included at leaf 353556 of 384,694. Version history · verify what your client received.

Tools (130)

Compare: most reliable retrieval servers · most reliable data servers · most reliable code servers · most reliable communication servers · most reliable devops servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the pg.ddx.io: the PostgreSQL community's memory MCP server down right now?

As of 2026-11-22 17:06 UTC, the pg.ddx.io: the PostgreSQL community's memory MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 4 minutes.

How many tools does pg.ddx.io: the PostgreSQL community's memory MCP server provide?

pg.ddx.io: the PostgreSQL community's memory MCP server advertises 130 tools, including animal_history, animal_owner_contributions, blame, blame_symbol, browse_by_date.

How do I install pg.ddx.io: the PostgreSQL community's memory MCP server?

Point your MCP client at this streamable-http endpoint: https://pg.ddx.io/mcp

Is the pg.ddx.io: the PostgreSQL community's memory MCP server safe to connect to an AI agent?

Glimind scanned all 130 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of pg.ddx.io: the PostgreSQL community's memory MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve