# Ddx Pg Archive MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.ddx.pg%2Farchive
Registry id: `mcp-registry/io.ddx.pg/archive`
Status: live (checked 2026-11-22T17:19:39.277Z)

## Measurements (30 days)

- Uptime: 99.9%
- Checks: 897
- Outages (90 days): 2

## Install

```json
{
  "mcpServers": {
    "ddx-pg-archive-mcp-server": {
      "type": "http",
      "url": "https://pg.ddx.io/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http ddx-pg-archive-mcp-server https://pg.ddx.io/mcp
```

## Tools (130)

- `animal_history`: One animal's runs, newest first; branch and since filter.
- `animal_owner_contributions`: Animals one owner runs (owner_name or owner_email; at least one): the branches each tracks, last status, first_seen_at and days since.
- `blame`: Per-line blame of a postgres file at any commit, as git blame. ignore_revs skips pgindent commits (.git-blame-ignore-revs); reverse adds the commit that removed
- `blame_symbol`: The commits that changed a symbol's lines in its file.
- `browse_by_date`: Threads active in a date range [since, until) on one list.
- `build_status_freshness`: cfbot data age: last_build_at (newest build finish), seen_at (newest result our sync saw), build_count. Old seen_at: our scraper stalled; old last_build_at, rec
- `buildfarm_overview`: Buildfarm health: animal count, recent runs, failing animals, top owners, OS / branch breakdown, freshness.
- `calendar_feeds`: Every calendar feed (iCalendar URL) with event counts: all, regions, countries, series, release cycle, teams, organisations.
- `check_upstream_status`: Was a pull request merged upstream: the patch series' latest head commit and any merge information.
- `code_index_status`: Code index statistics: files, symbols by kind and language, edges, communities.
- `code_search`: The postgres source at any commit, or across history (code-history index, byte-exact). match: literal (default), regex (^ $ per line) or identifier (all spellin
- `codebase_map`: File and symbol counts per directory.
- `combine_calendars`: Several calendar feeds (from calendar_feeds; 1-200) as one subscription: hash, feeds, https and webcal urls; stable per selection.
- `commit_buildfarm_status`: Buildfarm results for one postgres commit: per animal branch, status, failing stage, log url; rollup counts.
- `commit_history`: Everything linked to one commit: subject, author, date, sha, message, the Discussion: thread (participants as people and organizations), commitfest entry, Disco
- `commitfest_stats`: All commitfests: entries by status, top authors, and totals of people, commitfests and entries.
- `contribution_summary`: Per release: people, distinct commits, count of commits per role (canonical authoritative repos only), revert commits.
- `cross_reference`: What relates to one stored item. ref: Message-ID or URL, commit SHA or URL, docs URL or page, wiki URL or title, commitfest URL, CVE-YYYY-NNNNN, or feature:<wor
- `detect_changes`: The symbols that changed between two commits (file content hashes).
- `discussion_links`: A commit's Discussion / Closes / Fixes / Backpatch-through trailers: raw text and URL. For the mail itself: git_search mail_refs.
- `embedding_status`: Embedding coverage of a list: messages embedded, model, last run.
- `entry_branches`: Repository branches tracked for a commitfest entry: repo, branch_name, is_authoritative.
- `entry_history`: An entry's status across commitfests, matched by shared thread Message-ID (precise), else by title prefix (weak).
- `find_breaks`: Animals that failed on a branch between two commits, by run time (the buildfarm has no commit order).
- `find_contributions`: One person's contribution rows: commit SHAs and animals, each with role and release. By email, else name.
- `find_dead_code`: Functions and methods nothing calls (no incoming call edges).
- `find_entries_for_author`: Commitfest entries a person authored: email (exact) or name (substring, case-sensitive).
- `find_entries_for_thread`: Commitfest entries whose page links any message of the thread.
- `find_entries_with_failures_on`: An animal's recent failed runs, and commitfest entries failing in cfbot on branches it tracks (correlated by branch and time, not joined).
- `find_failing_patches`: Entries whose latest cfbot build fails on a platform: cf_id, title, entry_status, needs_rebase (newest version does not apply), commitfest_number.
- `find_failing_runs`: The newest failing buildfarm runs fleet-wide: what is broken now.
- `find_passing_long_pending`: Entries green on every platform that apply to master, not updated for min_days: why isn't it committed?
- `find_patches_by_platform_status`: Entries passing on one platform and failing on another (e.g. linux vs macos: a portability bug).
- `find_pattern`: Regex search of code symbol bodies (trigram-indexed).
- `find_rebase_needed_patches`: Entries cfbot says no longer apply to master: they need a rebase.
- `find_related_discussions`: Mail related to a commit, topic or PR. A postgres SHA: the mail referring to it (how_it_refers). Else a substring of subjects and Message-IDs, falling back to s
- `find_similar_messages`: Messages near one message by embedding: related or duplicate threads.
- `find_string_literals`: A literal in HEAD source, only inside "strings", after // or /* comments, or anywhere.
- `get_animal`: One animal: hardware, OS, compiler, owner, branches, last status, its last 20 runs.
- `get_attachment`: One attachment, whole, by 1-based index or filename substring. Text as text (a .patch applies with git apply), binary as base64; size = decoded bytes; url. Larg
- `get_author_messages`: One list's messages from a sender (name or address, as search's f:), newest first; since/until bound them.
- `get_callees`: What a symbol calls or references (forward call graph).
- `get_callers`: Who calls or references qualified_name, with file and lines. HEAD only; macros and function pointers are not followed.
- `get_commit`: One postgres commit (code-history index): message, trailers (names only), Discussion threads, back-patch siblings, first_releases (per branch: sha, release such
- `get_commitfest`: One commitfest: entries by status and its top authors.
- `get_communities`: Louvain clusters of the call graph: related symbols by functional area.
- `get_community`: One community and its symbols.
- `get_contributor`: A contributor by email (exact) or name (substring): canonical name, page hash, per-release counts by role, the 5 latest credited commits, animals owned. Cite ht
- `get_contributor_history`: Every list message from a sender (address or name).
- `get_dependents`: Transitive dependents: the blast radius if this symbol changes.
- `get_doc_page`: One docs page as text: url, path, body, fetched_at. Find the path with search_docs; cite the url.
- `get_entry`: One commitfest entry: title, status, commitfest, authors, reviewers, committer, mail threads, branches.
- `get_execution_flows`: Execution paths through the call graph from entry points.
- `get_impact`: Impact of changing a symbol: risk level, blast radius, communities and flows affected.
- `get_inbox_info`: A list's name, addresses, message_count (a cross-post counts on each list) and last activity.
- `get_inbox_stats`: A list's message counts per period, top authors, trends; total_messages; oldest_date/newest_date skip unparsable or impossible dates.
- `get_inbox_summary`: One list: total messages, top 10 posters, threads, date range, average messages per day over its life.
- `get_message`: One message: headers, in_reply_to/references, body (own words: quotes, forwards, inline patches, signature removed; full_text=true for all), attachments [{index
- `get_message_headers`: A message's headers as key/value pairs, all or one.
- `get_message_references`: A message's references: References/In-Reply-To and Message-IDs in its body, each looked up in the archive.
- `get_new_messages`: Messages after an article-number cursor, to poll without rescanning: after=0 first, then the returned last_article_num.
- `get_ontology`: What this server knows and which tool reads it: kinds of fact with attributes and counts, the design-history graph's relations, sources and confidence. Same as 
- `get_patch_branches`: Git branches made from a pull request's patch series.
- `get_patch_build_history`: One entry's cfbot build matrix: per job status, platform, config, log URL, at, started_at, seen_at; rollup: last_build_at, seen_at, passing/failing_platforms, a
- `get_patch_series`: Every iteration of a pull request posted to the lists.
- `get_raw_message`: A message's raw RFC 822 bytes.
- `get_repo_sync_stats`: A repository's commit cadence (median interval, suggested poll) and fetch log.
- `get_repository_summary`: One repository: commits, top 10 contributors, branches, languages (indexed symbols), most-touched paths (sampled).
- `get_signature`: A symbol's signature and doc comment.
- `get_source_info`: One list_sources source: kind, item_count, last_update, next_sync, freshness_status, description; a postgresql.org list also has poll (p_new, due, next_poll).
- `get_symbol`: A symbol by qualified name: source, signature, docs, file location.
- `get_tests_for`: Test symbols that reference a symbol.
- `get_thread`: The reply thread of a message (what In-Reply-To/References join to it), oldest first; root_message_id is its first message. grouping=subject: the whole subject 
- `get_thread_references`: A thread's cross-reference graph: Message-IDs cited in its bodies and the threads they point to.
- `get_wiki_history`: A wiki page's revisions.
- `get_wiki_page`: One wiki.postgresql.org page by title ("Don't Do This"): latest revision, author, date. Cite https://wiki.postgresql.org/wiki/<title>.
- `git_analyze_activity`: Commits per period: development pace.
- `git_analyze_authors`: Per author: commits, first and last date; by commit count.
- `git_analyze_bus_factor`: Files with the fewest distinct authors (knowledge silos).
- `git_analyze_churn`: Most often changed files.
- `git_analyze_coupling`: File pairs often changed together (hidden dependencies).
- `git_analyze_hotspots`: Churn per directory: the most changed areas.
- `git_blame`: A file's commit history (git log <rev> -- <path>), newest first: sha, commit_id, author, date, summary, status. Not per-line blame (blame). Renames not followed
- `git_diff`: Range mode (head_branch, optional base_branch: commits in head not base, filtered by author/message/path) or diff mode (from_commit, to_commit: unified diff).
- `git_log`: Commit history like git log, newest first; path, author (substring), since/until, branch (branch, tag or major) filter. Each: sha, commit_id, message, author, d
- `git_search`: Commit messages (or paths: search_in=paths) by keywords, best match first; every word, case-insensitive. Each commit: sha, commit_id, branch, branches (its bran
- `git_show_file`: A file at any commit (git show <rev>:<path>); an unknown rev or path is an error. Max 2000 lines a call (start_line/end_line; total_lines, cut). Returns sha and
- `grep_repository`: Literal search of the CURRENT source only (HEAD), like git grep -F. Files with repo_name, file_path, line_no, snippet. Other commits or history: code_search.
- `history-of`: For CI: given a diff, path, symbol, subject or feature, the most relevant default-branch commits, their mail discussion and the people involved.
- `hybrid_search`: Mailing-list search, BM25 over own words and semantic, blended per thread; every list unless inbox narrows it. Up to limit threads, best first, each its best me
- `hybrid_search_code`: Code search by keyword and meaning, fused (RRF). Needs embeddings.
- `list_animals`: Buildfarm animals by OS, branch, last status or owner; failing first, then by name.
- `list_branches`: A repository's branches: head commit, default.
- `list_commitfests`: Commitfests: status (open / in-progress / closed) and entry counts by status.
- `list_contributors`: Contributors from git trailers, author/committer headers and animal owners, most contributions first.
- `list_discord_channels`: Monitored Discord channels and their message counts.
- `list_doc_versions`: Documentation versions and page counts.
- `list_entries`: Commitfest entries (patch series) by status, commitfest or topic; paged.
- `list_files`: Files under a directory at any commit (code-history index) with line counts; depth folds deeper paths; glob filters.
- `list_inboxes`: Every list: name, message_count, latest_message_date, latest_import_date, listid, description.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
