Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.timescale/pg-aiguide

NPM · @TIGERDATA/PG-AIGUIDE · 3 COMPONENTS · SCANNED SEP 20

Comprehensive PostgreSQL documentation and best practices, including ecosystem tools

0 this week 49 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • Known CVEs were checked across the 301 of 308 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 301 of 308 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to timescale/pg-aiguide). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 15 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the io.github.timescale/pg-aiguide MCP server?

io.github.timescale/pg-aiguide runs locally as an npm package, launched with npx -y @tigerdata/pg-aiguide. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @tigerdata/pg-aiguide

# add to Claude Code
claude mcp add timescale-pg-aiguide -- npx -y @tigerdata/pg-aiguide
// .cursor/mcp.json
{
  "mcpServers": {
    "timescale-pg-aiguide": {
      "command": "npx",
      "args": [
        "-y",
        "@tigerdata/pg-aiguide"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "timescale-pg-aiguide": {
      "command": "npx",
      "args": [
        "-y",
        "@tigerdata/pg-aiguide"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add timescale-pg-aiguide -- npx -y @tigerdata/pg-aiguide
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "timescale-pg-aiguide": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@tigerdata/pg-aiguide"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add timescale-pg-aiguide --command npx --arg -y --arg @tigerdata/pg-aiguide
# ~/.hermes/config.yaml
mcp_servers:
  timescale-pg-aiguide:
    command: "npx"
    args: ["-y", "@tigerdata/pg-aiguide"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "timescale-pg-aiguide": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@tigerdata/pg-aiguide"
      ]
    }
  }
}
# add to Vellum
assistant mcp add timescale-pg-aiguide -t stdio -c npx -a -y @tigerdata/pg-aiguide
// mcp.json
{
  "mcpServers": {
    "timescale-pg-aiguide": {
      "command": "npx",
      "args": [
        "-y",
        "@tigerdata/pg-aiguide"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 9 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 8 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 7 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 6 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 5 Sept 26 0
    • Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan. security
    • Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess. functional
    • Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess. functional
  • 4 Sept 26 +3
    • CVE-2026-71850 no longer affects this package security
    • CVE-2026-71848 no longer affects this package security
    • CVE-2026-59892 no longer affects this package security
    • CVE-2026-54290 no longer affects this package security
    • CVE-2026-59896 no longer affects this package security
    • CVE-2026-59897 no longer affects this package security
    • CVE-2026-54288 no longer affects this package security
    • CVE-2026-54287 no longer affects this package security
    • CVE-2026-71849 no longer affects this package security
    • GHSA-frvp-7c67-39w9 no longer affects this package security
    • CVE-2026-59895 no longer affects this package security
    • CVE-2026-69207 no longer affects this package security
    • CVE-2026-54289 no longer affects this package security
    • CVE-2026-54286 no longer affects this package security
    • Known CVEs: fail → partial security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Security disclosure: fail → unverified functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Package version: 0.5.1 → 0.6.1 functional
  • 1 Sept 26 0
    • Security disclosure: unverified → fail functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/@tigerdata/pg-aiguide@0.6.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo timescale/pg-aiguide
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/timescale/pg-aiguide/.github/workflows/publish.yml@refs/tags/v0.6.1
Rekor log index 2715118280
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:fca8cbb8c507b2087c5dd9fb968be3acbc217f7799cc7b16895967d9195b9d5640e3d180b18c3ba30c14b6ca25f1467530217ab5ebb4efdaf60cf3060

Background: How many MCP packages publish verified provenance →

Dependencies 301 packages
Packages resolved 301
Deprecated 2
Stale 69
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the io.github.timescale/pg-aiguide MCP server?

io.github.timescale/pg-aiguide is an MCP server listed in the public MCP registry as io.github.timescale/pg-aiguide. Comprehensive PostgreSQL documentation and best practices, including ecosystem tools. This page covers its npm package (@tigerdata/pg-aiguide).

Is the io.github.timescale/pg-aiguide MCP server safe to use?

io.github.timescale/pg-aiguide scores 49 out of 100 on VerifyMCP. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the io.github.timescale/pg-aiguide MCP server still maintained?

io.github.timescale/pg-aiguide is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.timescale/pg-aiguide MCP server under?

io.github.timescale/pg-aiguide declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.