# io.github.timescale/pg-aiguide (remote · mcp.tigerdata.com)

Comprehensive PostgreSQL documentation and best practices, including ecosystem tools

- Trust score: 67/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.tigerdata.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/timescale-pg-aiguide/docs.md), [page](https://verifymcp.io/servers/timescale-pg-aiguide/docs)
- npm · `@tigerdata/pg-aiguide`: 42/100, [markdown](https://verifymcp.io/servers/timescale-pg-aiguide/tigerdata-pg-aiguide.md), [page](https://verifymcp.io/servers/timescale-pg-aiguide/tigerdata-pg-aiguide)
- oci · `ghcr.io/timescale/pg-aiguide:0.5.1`: 9/100, [markdown](https://verifymcp.io/servers/timescale-pg-aiguide/ghcr-io-timescale-pg-aiguide-0-5-1.md), [page](https://verifymcp.io/servers/timescale-pg-aiguide/ghcr-io-timescale-pg-aiguide-0-5-1)

## Channel facts

- Endpoint: `https://mcp.tigerdata.com/docs`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2190 tokens (~1095/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http timescale-pg-aiguide https://mcp.tigerdata.com/docs
```

### Codex

```toml
[mcp_servers.timescale-pg-aiguide]
url = "https://mcp.tigerdata.com/docs"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "timescale-pg-aiguide": {
      "type": "remote",
      "url": "https://mcp.tigerdata.com/docs",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add timescale-pg-aiguide --url https://mcp.tigerdata.com/docs --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  timescale-pg-aiguide:
    url: "https://mcp.tigerdata.com/docs"
```

### Other

```json
{
  "mcpServers": {
    "timescale-pg-aiguide": {
      "type": "http",
      "url": "https://mcp.tigerdata.com/docs"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 62)

First indexed and scored.

## MCP tools (2)

### `search_docs` (~211 tokens)

Search Documentation

Search documentation with hybrid semantic (vector) and keyword (BM25) search. Use semanticWeight to choose keyword-only (0), semantic-only (1), or a blend; mid values fuse rankings with RRF. Supports Tiger Cloud (TimescaleDB), PostgreSQL, and PostGIS.

Input parameters:

- `limit` (required): The maximum number of matches to return. Defaults to 20.
- `query` (string, required): The search query. Used for BM25 when keyword or hybrid search applies, and for the embedding when semantic or hybrid search applies.
- `semanticWeight` (required): Controls the balance between semantic and keyword search. 0 = keyword only, 0.5 = equal mix, 1 = semantic only. Default is 0.7 (favor semantic search).
- `source` (string, required): The documentation source to search. "tiger" for Tiger Cloud and TimescaleDB, "postgres" for PostgreSQL, "postgis" for PostGIS spatial extension. Specific versions provided with _X.X suffixes.

Output parameters:

- `results` (array)

### `view_skill` (~1979 tokens)

View Skill

Retrieve detailed skills for TimescaleDB operations and best practices.

\## Available Skills

\<available_skills>
[10]{namedescription}:
  design-postgis-tablesComprehensive PostGIS spatial table design reference covering geometry types, coordinate systems, spatial indexing, and performance patterns for location-based applications
  design-postgres-tables"Use this skill for general PostgreSQL table design.\n\n**Trigger when user asks to:**\n- Design PostgreSQL tables, schemas, or data models when creating new tables and when modifying existing ones.\n- Choose data types, constraints, or indexes for PostgreSQL\n- Create user tables, order tables, reference tables, or JSONB schemas\n- Understand PostgreSQL best practices for normalization, constraints, or indexing\n- Design update-heavy, upsert-heavy, or OLTP-style tables\n\n\n**Keywords:** PostgreSQL schema, table design, data types, PRIMARY KEY, FOREIGN KEY, indexes, B-tree, GIN, JSONB, constraints, normalization, identity columns, partitioning, row-level security\n\nComprehensive reference covering data types, indexing strategies, constraints, JSONB patterns, partitioning, and PostgreSQL-specific best practices.\n"
  find-hypertable-candidates"Use this skill to analyze an existing PostgreSQL database and identify which tables should be converted to Timescale/TimescaleDB hypertables.\n\n**Trigger when user asks to:**\n- Analyze database tables for hypertable conversion potential\n- Identify time-series or event tables in an existing schema\n- Evaluate if a table would benefit from Timescale/TimescaleDB\n- Audit PostgreSQL tables for migration to Timescale/TimescaleDB/TigerData\n- Score or rank tables for hypertable candidacy\n\n\n**Keywords:** hypertable candidate, table analysis, migration assessment, Timescale, TimescaleDB, time-series detection, insert-heavy tables, event logs, audit tables\n\nProvides SQL queries to analyze table statistics, index patterns, and query patterns. Includes scoring criteria (8+…

Input parameters:

- `path` (string, required): A relative path to a file or directory within the skill to view. If empty, will view the `SKILL.md` file by default. Use `.` to list the root directory of the skill.
- `skill_name` (string, required): The name of the skill to browse, or `.` to list all available skills.

Output parameters:

- `content` (string): The content of the file or directory listing.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/timescale-pg-aiguide/docs#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 67
- 2026-08-01: 66
- 2026-07-31: 66
- 2026-07-30: 65
- 2026-07-29: 64
- 2026-07-28: 64
- 2026-07-27: 63
- 2026-07-26: 62

## Links

- Remote endpoint: https://mcp.tigerdata.com/docs
- Repository: https://github.com/timescale/pg-aiguide
- Changelog RSS feed: https://verifymcp.io/servers/timescale-pg-aiguide/docs/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/timescale-pg-aiguide/docs/changelog.json
- HTML version of this page: https://verifymcp.io/servers/timescale-pg-aiguide/docs