Tiger MCP

OCI · GHCR.IO/TIMESCALE/TIGER-CLI:0.21.2 · SCANNED AUG 3

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

Available components

oci · ghcr.io/timescale/tiger-cli:0.21.2 38

−1 this week 38 38 Trust /100

Trust breakdown (6 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 →

Supply Chain Security0

Malware scan not yet available for this package.Unverified
CVE data not yet available for this package.Unverified
Install-script risk not yet assessed.Unverified
Dependency-health data not yet available.Unverified

Provenance & Transparency32

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
License check failed: no license is declared. See how to fix → Fail
Actively maintained (last published 17 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability64

AI-judged instruction clarity (excellent).Pass
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. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management23

Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

oci · ghcr.io/timescale/tiger-cli:0.21.2

Claude Codex opencode Hermes Other

# add to Claude Code

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

# add to Codex CLI

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/config.yaml

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

// mcp.json

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

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.

3 Aug 26 +4
- Stability: unverified → 0.23 ▲ functional
31 Jul 26 −5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
27 Jul 26 +31
- 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 functional
26 Jul 26 8

First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional

Show 3 earlier entries Hide earlier entries

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 3 Aug 2026 · Analysed oci/ghcr.io/timescale/tiger-cli:0.21.2

Provenance none

Ecosystem: oci · Outcome: none

Reason: no_attestation

MCP tools — 11 exposed · ~2,207 tokens

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.

Tool Tokens

db_execute_query Execute SQL Query ~306

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 Output Examples

Name	Type	Req	Description
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	yes	PostgreSQL query to execute
role	string	—	Database role/username to connect as
service_id	string	yes	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

Name	Type	Req	Description
execution_time	string	yes	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	yes	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.

No examples provided.

db_schema Show Database Schema ~282

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 Output Examples

Name	Type	Req	Description
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	yes	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…

Name	Type	Req	Description
schema	string	yes	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.

No examples provided.

service_create Create Database Service ~349

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 Output Examples

Name	Type	Req	Description
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.

Name	Type	Req	Description
message	string	yes	—
password_storage	null\|object	—	—
service	object	yes	—

No examples provided.

service_fork Fork Database Service ~431

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 Output Examples

Name	Type	Req	Description
cpu_memory	string	—	CPU and memory allocation combination. Choose from the available configurations. If not specified, inherits from source service.
fork_strategy	string	yes	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	yes	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.

Name	Type	Req	Description
message	string	yes	—
password_storage	null\|object	—	—
service	object	yes	—

No examples provided.

service_get Get Service Details ~92

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

Input Output Examples

Name	Type	Req	Description
service_id	string	yes	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.

Name	Type	Req	Description
service	object	yes	—

No examples provided.

service_list List Database Services ~31

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

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
services	null\|array	yes	—

No examples provided.

service_logs Get Service Logs ~237

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 Output Examples

Name	Type	Req	Description
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	yes	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.

Name	Type	Req	Description
logs	null\|array	yes	Log lines ordered from oldest to newest. Each line is prefixed with an RFC3339 timestamp followed by the log message.

No examples provided.

service_resize Resize Database Service ~155

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 Output Examples

Name	Type	Req	Description
cpu_memory	string	yes	CPU and memory allocation combination. Choose from the available configurations.
service_id	string	yes	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…

Name	Type	Req	Description
message	string	yes	—
resources	null\|object	—	—
status	string	yes	Current service status after resize operation

No examples provided.

service_start Start Database Service ~121

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 Output Examples

Name	Type	Req	Description
service_id	string	yes	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…

Name	Type	Req	Description
message	string	yes	—
status	string	yes	Current service status after start operation

No examples provided.

service_stop Stop Database Service ~119

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 Output Examples

Name	Type	Req	Description
service_id	string	yes	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,…

Name	Type	Req	Description
message	string	yes	—
status	string	yes	Current service status after stop operation

No examples provided.

service_update_password Update Service Password ~84

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

Input Output Examples

Name	Type	Req	Description
password	string	yes	The new password for the 'tsdbadmin' user. Must be strong and secure.
service_id	string	yes	Unique identifier of the service (10-character alphanumeric string). Use service_list to find service IDs.

Name	Type	Req	Description
message	string	yes	—
password_storage	null\|object	—	—

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	8
27 Jul	39
28 Jul	39
29 Jul	39
30 Jul	39
31 Jul	34
1 Aug	34
2 Aug	34
3 Aug	38