detect_changes

2 MCP servers expose a detect_changes tool: Codebase Memory and pg.ddx.io: the PostgreSQL community's memory. Their input schemas differ, so compare them below before picking one.

Servers exposing detect_changes

• Codebase MemoryA · 99stdio

  From the publisher:Map git diff to affected symbols + blast radius with risk classification.

  Install Codebase Memory →
• pg.ddx.io: the PostgreSQL community's memoryD · 33HTTP

  From the publisher:Detect which symbols changed between two commits by comparing file content hashes.

  Parameter	Type	Description
  from_commit*	string	Base commit: a SHA (>= 7 hex), branch, tag, major version (17, 9.6), <ref>~N, or a commit_id from another tool, or a commit URL (gitweb, git.postgresql.org, GitHub, pg.ddx.io).
  repository	string	Repository name, e.g. pgbouncer. Defaults to postgres when omitted. Aliases: repo, repo_name.
  to_commit	string	Target commit: a SHA (>= 7 hex), branch, tag, major version (17, 9.6), <ref>~N, or a commit_id from another tool, or a commit URL (gitweb, git.postgresql.org, GitHub, pg.ddx.io). Default HEAD.

  Install pg.ddx.io: the PostgreSQL community's memory →

Tool lists are read from the live servers (or, for packaged servers, from their documentation) each morning, so this reflects what they exposed at the last refresh. Search all tools.