Skip to content

MCP servers › io.github.tombaldwin › pgman

MCP server · registry snapshot 2026-11-17 · last checked 2026-11-17

pgman MCP server

Registry name io.github.tombaldwin/pgman

by tombaldwin · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗

PostgreSQL for coding agents: schema, read-only queries, EXPLAIN, masked dumps, confirmed writes. — the publisher's description

5 of 5 record checks metversion 0.5.4Ruststandard input/output

Summary

io.github.tombaldwin/pgman is a local MCP server listed in the official MCP registry at version 0.5.4, under the namespace of the GitHub account tombaldwin. Its linked repository, github.com/tombaldwin/pgman, belongs to the same GitHub account.

Record checks

5 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: not an npm or PyPI package
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
local package
Transport
standard input/output
Your own values
none declared (not a guarantee)
Package
Cargo
Repository
public
Last tested
not tested

Tool list

Not read: It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.

Add to your client

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
0.5.4, published 2026-11-16 (registry, as of the 2026-11-17 snapshot)
First listed version
2026-11-09 (earliest version still in the registry; older removed versions would be earlier)
Version history
4 versions listed, 2026-11-09 to 2026-11-16; 4 in the 90 days before the 2026-11-17 snapshot.
Most recent 4 versions
  • 0.5.4 · 2026-11-16
  • 0.5.3 · 2026-11-14
  • 0.5.2 · 2026-11-12
  • 0.5.1 · 2026-11-09
(versions still listed in the registry only)
Registry data
snapshot 2026-11-17
Package and repository
checked 2026-11-17

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 0.5.3 (published 2026-11-14) → 0.5.4 (published 2026-11-16), between the registry lists of 2026-11-16 and 2026-11-17.

The publisher’s GitHub release note for v0.5.4 (“pgman v0.5.4”), published 2026-11-16.

Read the release note (the publisher’s text, shown as plain text)
### Added

- Patch files can be read at a git ref — a tag, branch or SHA — instead
  of the working tree: `ref` on MCP's `apply_patches` and
  `pending_patches`, `pgman apply --ref`. The ref is resolved once to a
  commit, named in the plan, the confirmation, the result and the audit
  log line, and read through `git ls-tree` / `git cat-file`; nothing is
  checked out.
- A plan or `pending_patches` read from a git checkout's working tree
  warns about what differs from its commit: patch files not committed
  or changed since, a branch other than the default, commits behind its
  upstream (as of the last fetch), and a remote database.
- `pending_patches` without a `[patches]` block takes the settings from
  an `environments.toml` `version_table` whose patches directory is
  inside the project, when all such agree; a missing setting's error
  names every missing one and a block to paste.

### Changed

- MCP `apply_patches` refuses a remote database's patches from a
  checkout's working tree without `ref`; a local database, or a patches
  directory outside git, is as before. An apply at the same ref as the
  session's dry run that finds another commit is refused. Any other run
  after a dry run that reads another commit (another spelling of the
  ref, another ref, the working tree) opens its confirmation by saying
  so.
- `apply_patches`' confirmation names where the files came from: the
  ref and its commit, or the checkout's working tree with its branch
  and commit. A protected environment over loopback warns that its
  files aren't a named commit.
- A patch plan reads every file once, before connecting, and runs the
  texts it read. A patch file over 16 MB is refused by its size, where
  `pending_patches` used to read only its first 1 MB.

### Security

- git, wherever pgman runs it in a checkout, ignores replace refs (which
  could make a named commit yield another commit's files) and fetches
  nothing: a partial clone's missing object reads as missing, rather
  than being fetched through the remote's transport from the checkout's
  config (`core.sshCommand`, a credential helper).

The release on GitHub

Source: the official MCP Registry list on 2026-11-16 and on 2026-11-17; release notes from the GitHub Releases API, checked 2026-11-17.

What it is

How do I add it to my client?

Config from the registry entry
  • No config: no ready-made command for the Cargo crate; use the publisher's instructions.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-17. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-17. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-17. Source: read 2026-11-17.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-17. Source: read 2026-11-17.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Repository github.com/tombaldwin/pgmanOpens publiclymatchesapi.github.com · 2026-11-17

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.tombaldwin · 5 servers
GitHub owner
a personal account (tombaldwin)
Repository
github.com/tombaldwin/pgman
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
SECURITY.md

Source: the registry entry and api.github.com · 2026-11-17; security policy read from GitHub · 2026-11-09.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

5 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: not an npm or PyPI package
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
  • Does not applyPackage names its licence with a standard (SPDX) identifierNot an npm or PyPI package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnNot an npm or PyPI package.
  • Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
  • Does not applyNo known critical or high advisory in the package or its dependenciesNot an npm or PyPI package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-17 (security policy 2026-11-09). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.tombaldwin/pgman

Answered from the data above

Who publishes io.github.tombaldwin/pgman?

The registry ties the namespace io.github.tombaldwin to the GitHub account tombaldwin; only its owner can publish under it. Its linked repository, github.com/tombaldwin/pgman, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.tombaldwin/pgman safe to install?

We do not rate servers as safe or unsafe. 5 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.tombaldwin/pgman been security tested?

No. It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's.

Does io.github.tombaldwin/pgman publish a security policy?

Yes: its repository has a public security policy (github.com/tombaldwin/pgman/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Where is the source code of io.github.tombaldwin/pgman?

In github.com/tombaldwin/pgman, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. — our limit

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-17; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
api.github.com · 2026-11-17
Hosting type
registry · 2026-11-17
MCP capability
not checked
not read (no session)
Transport
standard input/output
registry · 2026-11-17
Required credentials
none declared
registry · 2026-11-17 · no declaration is not a guarantee
Package registry
registry · 2026-11-17
Freshness
0–30 days
registry updatedAt · 2026-11-17
Lifecycle status
registry · 2026-11-17
License class
does not apply
package ecosystem not queried by this layer (cargo); only npm and PyPI are supported here
Integrity hash
does not apply
package ecosystem not queried by this layer (cargo); only npm and PyPI are supported here
Signature / provenance
does not apply
package ecosystem not queried by this layer (cargo); only npm and PyPI are supported here
Dependency advisories
not checked
only npm and PyPI packages are audited
Popularity
does not apply
package ecosystem not queried by this layer (cargo); only npm and PyPI are supported here
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-11-17
Maintenance
api.github.com · 2026-11-17
Environment
your machine
where it runs, from the hosting type · 2026-11-17

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.tombaldwin/pgman: MCP server record.” Data checked 2026-11-17. https://protocolprobe.com/mcp/servers/io.github.tombaldwin/pgman

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 5 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.tombaldwin/pgman)](https://protocolprobe.com/mcp/servers/io.github.tombaldwin/pgman)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology