# Tiger MCP (oci · ghcr.io/timescale/tiger-cli:0.21.2)

Provides programmatic access to Tiger Cloud services, databases, and documentation.

- Trust score: 38/100 (low)
- Change this week: −1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- oci · `ghcr.io/timescale/tiger-cli:0.21.2`: 38/100 (this document), [markdown](https://verifymcp.io/servers/timescale-tiger-cli/ghcr-io-timescale-tiger-cli-0-21-2.md), [page](https://verifymcp.io/servers/timescale-tiger-cli/ghcr-io-timescale-tiger-cli-0-21-2)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/timescale/tiger-cli:0.21.2`
- Transport: `stdio`

## Trust breakdown

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. 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.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - CVE data not yet available for this package.
  - Install-script risk not yet assessed.
  - Dependency-health data not yet available.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 17 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2262 tokens (~205/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add timescale-tiger-cli -- docker run --rm -i ghcr.io/timescale/tiger-cli:0.21.2
```

### Codex

```bash
codex mcp add timescale-tiger-cli -- docker run --rm -i ghcr.io/timescale/tiger-cli:0.21.2
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "timescale-tiger-cli": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/timescale/tiger-cli:0.21.2"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  timescale-tiger-cli:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/timescale/tiger-cli:0.21.2"]
```

### Other

```json
{
  "mcpServers": {
    "timescale-tiger-cli": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/timescale/tiger-cli:0.21.2"
      ]
    }
  }
}
```

## 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-03 (score 38, +4)

- [functional improvement] Stability: unverified → 0.23

### 2026-07-31 (score 34, −5)

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

### 2026-07-27 (score 39, +31)

- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: excellent
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: fail

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

First indexed and scored.

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

## MCP tools (11)

### `db_execute_query` (~306 tokens)

Execute SQL Query

Execute SQL queries against a service database.

Connects to a PostgreSQL database service in Tiger Cloud and executes the provided SQL query, returning the results with column information, row data, and execution metadata.

Multi-statement queries (semicolon-separated) are supported when no parameters are provided. All result sets are returned. By default, statements execute in an implicit transaction that automatically commits on success or rolls back on error. Explicit transactions (opened with BEGIN) must be explicitly committed with COMMIT, or they roll back when the connection closes.

Process data in the database, not in your context: aggregate, filter, sort/limit, and join in SQL rather than fetching raw rows.

WARNING: Can execute any SQL statement including INSERT, UPDATE, DELETE, and DDL commands. Always review queries before execution.

Input parameters:

- `parameters` (null|array): Query parameters. Values are substituted for $1, $2, etc. placeholders in the query.
- `pooled` (boolean): Use connection pooling (if available)
- `query` (string, required): PostgreSQL query to execute
- `role` (string): Database role/username to connect as
- `service_id` (string, required): Unique identifier of the service (10-character alphanumeric string). Use service_list to find service IDs. A read replica set ID is also accepted here — passing one runs the query against that read r…
- `timeout_seconds` (integer): Query timeout in seconds

Output parameters:

- `execution_time` (string): Execution time as a human-readable duration string
- `notice` (string): Present only when results were truncated. Actionable guidance for getting the needed data via SQL (aggregate, filter, paginate) instead of re-running the query.
- `result_sets` (null|array): Array of result sets returned. For single-statement queries, this array will contain one element. For multi-statement queries, this array will contain one element per statement.
- `truncated` (boolean): True when any result set was truncated to limit the amount of data returned. See notice for guidance.
- `warning` (string): Present when connection pooling was requested for a read replica that has none; the query ran over a direct connection instead.

### `db_schema` (~282 tokens)

Show Database Schema

Display the schema of a service database.

Connects to a PostgreSQL/TimescaleDB service in Tiger Cloud and returns its schema as readable text: tables (regular, partitioned, and foreign), views, materialized views, enum types, functions, procedures, indexes, triggers, and TimescaleDB hypertable and continuous aggregate metadata. Only objects the connecting role can access are returned.

By default only user-facing schemas and objects are shown; view/routine definitions and object comments are omitted unless requested. The connection is opened in immutable read-only mode.

Input parameters:

- `comments` (boolean): Include object comments (COMMENT ON text).
- `definitions` (boolean): Include full object definitions (view SELECTs, function/procedure bodies).
- `internal` (boolean): Include system schemas (pg_*, information_schema, TimescaleDB internals) and extension-owned objects.
- `pooled` (boolean): Use connection pooling (if available)
- `role` (string): Database role/username to connect as
- `schema` (string): Restrict output to a single schema (namespace). When omitted, all accessible schemas are returned.
- `service_id` (string, required): Unique identifier of the service (10-character alphanumeric string). Use service_list to find service IDs. A read replica set ID is also accepted here — passing one introspects that read replica inst…

Output parameters:

- `schema` (string): The database schema rendered as human-readable text, grouped under a SCHEMA header per namespace.
- `warning` (string): Present when connection pooling was requested for a read replica that has none; the schema was read over a direct connection instead.

### `service_create` (~349 tokens)

Create Database Service

Create a new database service in Tiger Cloud with specified type, compute resources, region, and HA options.

The default type of service created depends on the user's plan:
\- Free plan: Creates a service with shared CPU/memory and the 'time-series' and 'ai' add-ons
\- Paid plans: Creates a service with 0.5 CPU / 2 GB memory and the 'time-series' add-on

WARNING: Creates billable resources.

Input parameters:

- `addons` (null|array): Array of addons to enable for the service. 'time-series' enables TimescaleDB, 'ai' enables AI/vector extensions. Use empty array for PostgreSQL-only.
- `cpu_memory` (string): CPU and memory allocation combination. Choose from the available configurations.
- `name` (string): Human-readable name for the service (auto-generated if not provided)
- `region` (null|string): AWS region where the service will be deployed. Choose the region closest to your users for optimal performance.
- `replicas` (integer): Number of high-availability replicas for fault tolerance. Higher replica counts increase cost but improve availability.
- `set_default` (boolean): Whether to set the newly created service as the default service. When true, the service will be set as the default for future commands.
- `wait` (boolean): Whether to wait for the service to be fully ready before returning. Default is false (recommended). Only set to true if your next steps require connecting to or querying this database. When true, wai…
- `with_password` (boolean): Whether to include the password in the response and connection string. NEVER set to true unless the user explicitly asks for the password.

Output parameters:

- `message` (string)
- `password_storage` (null|object)
- `service` (object)

### `service_fork` (~431 tokens)

Fork Database Service

Fork an existing database service to create a new independent copy.

You must specify a fork strategy:
\- 'NOW': Fork at the current database state (creates new snapshot or uses WAL replay)
\- 'LAST_SNAPSHOT': Fork at the last existing snapshot (faster fork)
\- 'PITR': Fork at a specific point in time (requires target_time parameter)

By default:
\- Name will be auto-generated as '{source-service-name}-fork'
\- CPU and memory will be inherited from the source service
\- The forked service will be set as the default service

WARNING: Creates billable resources.

Input parameters:

- `cpu_memory` (string): CPU and memory allocation combination. Choose from the available configurations. If not specified, inherits from source service.
- `fork_strategy` (string, required): Fork strategy: 'NOW' creates fork at current state, 'LAST_SNAPSHOT' uses last existing snapshot (faster), 'PITR' allows point-in-time recovery to specific timestamp (requires target_time parameter)
- `name` (string): Human-readable name for the forked service (auto-generated if not provided)
- `service_id` (string, required): Unique identifier of the service (10-character alphanumeric string). Use service_list to find service IDs.
- `set_default` (boolean): Whether to set the newly forked service as the default service. When true, the forked service will be set as the default for future commands.
- `target_time` (null|string): Target timestamp for point-in-time recovery (RFC3339 format, e.g., '2025-01-15T10:30:00Z'). Only used when fork_strategy is 'PITR'.
- `wait` (boolean): Whether to wait for the forked service to be fully ready before returning. Default is false (recommended). Only set to true if your next steps require connecting to or querying this database. When tr…
- `with_password` (boolean): Whether to include the password in the response and connection string. NEVER set to true unless the user explicitly asks for the password.

Output parameters:

- `message` (string)
- `password_storage` (null|object)
- `service` (object)

### `service_get` (~92 tokens)

Get Service Details

Get detailed information for a specific database service. Returns connection endpoints, replica configuration, resource allocation, creation time, and status.

Input parameters:

- `service_id` (string, required): Unique identifier of the service (10-character alphanumeric string). Use service_list to find service IDs.
- `with_password` (boolean): Whether to include the password in the response and connection string. NEVER set to true unless the user explicitly asks for the password.

Output parameters:

- `service` (object)

### `service_list` (~31 tokens)

List Database Services

List all database services in your Tiger Cloud project. Returns services with status, type, region, and resource allocation.

Output parameters:

- `services` (null|array)

### `service_logs` (~237 tokens)

Get Service Logs

View logs for a database service.

Fetches and displays logs from the specified service. By default, shows the last 100 log entries.

Supports filtering by time (via since/until parameters) and node (for services with HA replicas).

Input parameters:

- `node` (null|integer): Specific service node to fetch logs from (for services with HA replicas). If not provided, logs from the primary node will be fetched.
- `service_id` (string, required): Unique identifier of the service (10-character alphanumeric string). Use service_list to find service IDs.
- `since` (null|string): Fetch logs after this timestamp (RFC3339 format, e.g., '2024-01-15T09:00:00Z'). If not provided, only the tail parameter limits how far back logs are fetched.
- `tail` (integer): Number of log lines to return. Defaults to 100.
- `until` (null|string): Fetch logs before this timestamp (RFC3339 format, e.g., '2024-01-15T10:00:00Z'). If not provided, fetches logs up to the current time.

Output parameters:

- `logs` (null|array): Log lines ordered from oldest to newest. Each line is prefixed with an RFC3339 timestamp followed by the log message.

### `service_resize` (~155 tokens)

Resize Database Service

Resize a database service by changing its CPU and memory allocation.

This tool changes the compute resources allocated to your database service. The service
may be temporarily unavailable during the resize operation.

WARNING: Creates billable resource changes. Increasing resources will increase costs.

Input parameters:

- `cpu_memory` (string, required): CPU and memory allocation combination. Choose from the available configurations.
- `service_id` (string, required): Unique identifier of the service (10-character alphanumeric string). Use service_list to find service IDs.
- `wait` (boolean): Whether to wait for the service to be done resizing before returning. Default is false (recommended). Only set to true if your next steps require connecting to or querying this database. When true, w…

Output parameters:

- `message` (string)
- `resources` (null|object)
- `status` (string): Current service status after resize operation

### `service_start` (~121 tokens)

Start Database Service

Start a stopped database service.

This operation starts a service that is currently in a stopped/paused state. The service will transition to a ready state and become available for connections.

Input parameters:

- `service_id` (string, required): Unique identifier of the service (10-character alphanumeric string). Use service_list to find service IDs.
- `wait` (boolean): Whether to wait for the service to be fully started before returning. Default is false (recommended). Only set to true if your next steps require connecting to or querying this database. When true, w…

Output parameters:

- `message` (string)
- `status` (string): Current service status after start operation

### `service_stop` (~119 tokens)

Stop Database Service

Stop a running database service.

This operation stops a service that is currently running. The service will transition to a stopped/paused state and will no longer accept connections.

Input parameters:

- `service_id` (string, required): Unique identifier of the service (10-character alphanumeric string). Use service_list to find service IDs.
- `wait` (boolean): Whether to wait for the service to be fully stopped before returning. Default is false (recommended). Only set to true if your next steps require confirmation that the service is stopped. When true,…

Output parameters:

- `message` (string)
- `status` (string): Current service status after stop operation

### `service_update_password` (~84 tokens)

Update Service Password

Update master password for 'tsdbadmin' user of a database service. Takes effect immediately. May terminate existing connections.

Input parameters:

- `password` (string, required): The new password for the 'tsdbadmin' user. Must be strong and secure.
- `service_id` (string, required): Unique identifier of the service (10-character alphanumeric string). Use service_list to find service IDs.

Output parameters:

- `message` (string)
- `password_storage` (null|object)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/timescale-tiger-cli/ghcr-io-timescale-tiger-cli-0-21-2#diagnostics

## Score history

- 2026-08-03: 38
- 2026-08-02: 34
- 2026-08-01: 34
- 2026-07-31: 34
- 2026-07-30: 39
- 2026-07-29: 39
- 2026-07-28: 39
- 2026-07-27: 39
- 2026-07-26: 8

## Links

- Repository: https://github.com/timescale/tiger-cli
- Changelog RSS feed: https://verifymcp.io/servers/timescale-tiger-cli/ghcr-io-timescale-tiger-cli-0-21-2/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/timescale-tiger-cli/ghcr-io-timescale-tiger-cli-0-21-2/changelog.json
- HTML version of this page: https://verifymcp.io/servers/timescale-tiger-cli/ghcr-io-timescale-tiger-cli-0-21-2