# Statable (npm · @statable/mcp)

Privacy-first, cookieless web analytics: traffic, sources, pages, goals, funnels and site setup.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `mcp.statable.com`: 32/100, [markdown](https://verifymcp.io/servers/com-statable-analytics/mcp.md), [page](https://verifymcp.io/servers/com-statable-analytics/mcp)
- npm · `@statable/mcp`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-statable-analytics/statable-mcp.md), [page](https://verifymcp.io/servers/com-statable-analytics/statable-mcp)

## Channel facts

- Registry: `npm`
- Package: `@statable/mcp`
- Version: `0.1.0`
- 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-09-24.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 19 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4444 tokens (~177/item across 25 items; 25 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 25 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Statable MCP server?

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

### Claude

```bash
claude mcp add com-statable-analytics -- npx -y @statable/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-statable-analytics": {
      "command": "npx",
      "args": [
        "-y",
        "@statable/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-statable-analytics": {
      "command": "npx",
      "args": [
        "-y",
        "@statable/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-statable-analytics -- npx -y @statable/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-statable-analytics": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@statable/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-statable-analytics --command npx --arg -y --arg @statable/mcp
```

### Hermes

```yaml
mcp_servers:
  com-statable-analytics:
    command: "npx"
    args: ["-y", "@statable/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-statable-analytics": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@statable/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-statable-analytics -t stdio -c npx -a -y @statable/mcp
```

### Other

```json
{
  "mcpServers": {
    "com-statable-analytics": {
      "command": "npx",
      "args": [
        "-y",
        "@statable/mcp"
      ]
    }
  }
}
```

## 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-09-23 (score 78, +1)

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

### 2026-09-21 (score 77, +1)

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

### 2026-09-19 (score 76, +1)

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

### 2026-09-17 (score 75, +1)

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

### 2026-09-15 (score 74, +1)

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

### 2026-09-13 (score 73, +1)

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

### 2026-09-11 (score 72, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-09-05 (score 69, +15)

- [security improvement] Malware scan: unverified → pass

## MCP tools (25)

### `list_sites` (~302 tokens)

List the sites this API key can read. Response: {"sites":[{"site_id":123,"name":"<as entered by the owner — often a full URL like https://example.com/>","hash":"07k1eD84d2","timezone":"Europe/Amsterdam","hobby":false,"stats_start_date":"YYYY-MM-DD"|null,"created_at":"RFC3339"}]}. hobby=true is a free-plan site: it counts only through the bundled /t/ script get_tracking_snippet returns, so install that snippet verbatim. Use site_id with the other tools. With date_range each site also carries metrics NESTED under stats.metrics (never flat on the site object). Units: visit_duration = average seconds per visit; bounce_rate = percent 0-100; views_per_visit = pageviews/visits ratio; visitors/pageviews/visits = counts. Stats period boundaries are server-time approximations; use query_stats for timezone-exact numbers.

Input parameters:

- `date_range` (string): Optional. "7d"/"30d"/"month"/"realtime" or "Nd" for the last N days (1-90), e.g. "7d". Each site then gets {"stats":{"date_range":"7d","metrics":{"visitors":N,"pageviews":N,"visits":N,"visit_duration…

### `query_stats` (~604 tokens)

Run a read-only analytics query for one site: aggregate totals, a time series, or a top-N breakdown. Returns {"results":[{"dimensions":{...omitted for aggregates},"metrics":{...}}]}. All dates and time buckets are in the site's own timezone (see list_sites .timezone). The event:name breakdown lists custom events (data-statable-event); its `events` metric is the raw event count. The event:goal breakdown lists the site's configured goals with `visitors` (converters), `events` (conversions) and `conversion_rate` (percent). `events`/`conversion_rate` are breakdown-only (rejected on aggregate/time-series or a dimension that doesn't compute them). Units: visit_duration = average seconds per visit; bounce_rate = percent 0-100; views_per_visit = pageviews/visits ratio; visitors/pageviews/visits = counts.

Input parameters:

- `compare` (string|array): "previous_period" (equal-length window before date_range) or a custom ["YYYY-MM-DD","YYYY-MM-DD"] pair. Adds a compare {value, change%} block: per-metric (aggregate), per-row (breakdown; not event:st…
- `date_range` (string|array, required): Preset "7d" or "30d" (last N full days), "month" (current calendar month to date; the first bucket may land on the prior month's last day), "realtime" (last ~30 min — pair with the time:minute dimens…
- `dimensions` (array): Zero = aggregate; one time dimension (time, time:hour, time:day, time:week, time:month) = time series; one breakdown dimension = top-N. Besides the enum you may also pass a dynamic 'event:props:<key>…
- `filters` (array)
- `limit` (integer): Breakdown only. Default 100, max 1000.
- `metrics` (array, required)
- `site` (string): Numeric site_id (preferred, from list_sites) or a domain, e.g. example.com — scheme, www. and path are ignored when matching. If several sites share the domain the call fails and lists their site_ids…

### `top_pages` (~167 tokens)

Top pages by visitors for a site. Returns {"results":[{"dimensions":{"event:page":"/path"},"metrics":{"pageviews":N,"visitors":N}}]}.

Input parameters:

- `limit` (integer): Default 100, max 1000.
- `period` (string): "7d"/"30d", or any "Nd" = last N full days (N = 1..90); "month" = current calendar month to date. Default 30d.
- `site` (string): Numeric site_id (preferred, from list_sites) or a domain, e.g. example.com — scheme, www. and path are ignored when matching. If several sites share the domain the call fails and lists their site_ids…

### `top_sources` (~170 tokens)

Top traffic sources by visitors for a site. Returns {"results":[{"dimensions":{"visit:source":"Google"},"metrics":{"visitors":N,"bounce_rate":percent0to100}}]}.

Input parameters:

- `limit` (integer): Default 100, max 1000.
- `period` (string): "7d"/"30d", or any "Nd" = last N full days (N = 1..90); "month" = current calendar month to date. Default 30d.
- `site` (string): Numeric site_id (preferred, from list_sites) or a domain, e.g. example.com — scheme, www. and path are ignored when matching. If several sites share the domain the call fails and lists their site_ids…

### `top_countries` (~197 tokens)

Top countries by visitors for a site. Returns {"results":[{"dimensions":{"visit:country":"US"},"labels":{"visit:country":"United States"},"metrics":{"visitors":N}}]} — the dimension value is the ISO alpha-2 code (drops straight into a country filter); the display name is in labels.

Input parameters:

- `limit` (integer): Default 100, max 1000.
- `period` (string): "7d"/"30d", or any "Nd" = last N full days (N = 1..90); "month" = current calendar month to date. Default 30d.
- `site` (string): Numeric site_id (preferred, from list_sites) or a domain, e.g. example.com — scheme, www. and path are ignored when matching. If several sites share the domain the call fails and lists their site_ids…

### `top_custom_events` (~194 tokens)

Top custom events (data-statable-event) by count for a site — pageview/engagement excluded. Returns {"results":[{"dimensions":{"event:name":"Signup"},"metrics":{"events":N,"visitors":N}}]}, where events is the raw occurrence count and visitors is unique users who triggered it.

Input parameters:

- `limit` (integer): Default 100, max 1000.
- `period` (string): "7d"/"30d", or any "Nd" = last N full days (N = 1..90); "month" = current calendar month to date. Default 30d.
- `site` (string): Numeric site_id (preferred, from list_sites) or a domain, e.g. example.com — scheme, www. and path are ignored when matching. If several sites share the domain the call fails and lists their site_ids…

### `top_goals` (~199 tokens)

The site's configured goals ranked by conversions. Returns {"results":[{"dimensions":{"event:goal":"Signup"},"metrics":{"visitors":N,"events":N,"conversion_rate":percent0to100}}]}, where visitors is unique converters, events is total conversions, and conversion_rate is visitors as a percent of all visitors in the period.

Input parameters:

- `limit` (integer): Default 100, max 1000.
- `period` (string): "7d"/"30d", or any "Nd" = last N full days (N = 1..90); "month" = current calendar month to date. Default 30d.
- `site` (string): Numeric site_id (preferred, from list_sites) or a domain, e.g. example.com — scheme, www. and path are ignored when matching. If several sites share the domain the call fails and lists their site_ids…

### `list_goals` (~94 tokens)

The goals CONFIGURED on a site — what it measures, not how those goals performed. Use top_goals for conversion numbers. Response: {"goals":[{"id":7,"name":"Signup","event_name":"Signup"|null,"path":"/thanks"|null,"operator":"e|b|c","scroll_depth":N|null}]}.

Input parameters:

- `site` (string|integer, required): site_id from list_sites.

### `list_prop_keys` (~190 tokens)

List the custom-property keys a site has recorded (with the event each belongs to) — discovery for the event:props:<key> breakdown in query_stats. Returns {"props":[{"key":"plan","event":"Signup","count":N,"first_seen":"RFC3339"}]}.

Input parameters:

- `period` (string|array): "7d"/"30d", or any "Nd" = last N full days (N = 1..90); "month" = current calendar month to date. Default 30d. Or a custom ["YYYY-MM-DD","YYYY-MM-DD"] pair.
- `site` (string): Numeric site_id (preferred, from list_sites) or a domain, e.g. example.com — scheme, www. and path are ignored when matching. If several sites share the domain the call fails and lists their site_ids…

### `list_funnels` (~114 tokens)

List the conversion funnels configured for a site (discovery — get a funnel_id for funnel_report). Returns {"funnels":[{"id":45,"name":"Signup flow","scope":"visitor","steps_count":3}]}.

Input parameters:

- `site` (string): Numeric site_id (preferred, from list_sites) or a domain, e.g. example.com — scheme, www. and path are ignored when matching. If several sites share the domain the call fails and lists their site_ids…

### `funnel_report` (~302 tokens)

Run a saved conversion funnel and return its per-step result (NON-tabular). Returns {"funnel":{"id","name","scope"},"entering":N,"all_visitors":N,"steps":[{"index":0,"name":"Visited /pricing","kind":"page","visitors":N,"conversion_rate":percent0to100,"dropoff":N}, ...]}. steps are ORDERED; conversion_rate is cumulative vs the first step (entering), NOT step-to-step; dropoff is visitors lost vs the previous step. Get funnel_id from list_funnels first.

Input parameters:

- `filters` (array): Optional SEGMENT filters (session-level only: country/browser/os/device/source/channel/utm_*/entry_page/exit_page/hostname). Event-level fields are rejected.
- `funnel_id` (integer, required): Funnel id from list_funnels.
- `period` (string|array): "7d"/"30d", or any "Nd" = last N full days (N = 1..90); "month" = current calendar month to date. Default 30d. Or a custom ["YYYY-MM-DD","YYYY-MM-DD"] pair.
- `site` (string): Numeric site_id (preferred, from list_sites) or a domain, e.g. example.com — scheme, www. and path are ignored when matching. If several sites share the domain the call fails and lists their site_ids…

### `current_visitors` (~98 tokens)

Realtime count of unique visitors active in the last 5 minutes for a site. Returns {"site_id":123,"visitors":N}.

Input parameters:

- `site` (string): Numeric site_id (preferred, from list_sites) or a domain, e.g. example.com — scheme, www. and path are ignored when matching. If several sites share the domain the call fails and lists their site_ids…

### `visitors_over_time` (~163 tokens)

Daily visitors and pageviews time series for a site, in the site's own timezone. Returns {"results":[{"dimensions":{"time:day":"YYYY-MM-DD"},"metrics":{"visitors":N,"pageviews":N}}]}.

Input parameters:

- `period` (string): "7d"/"30d", or any "Nd" = last N full days (N = 1..90); "month" = current calendar month to date. Default 30d.
- `site` (string): Numeric site_id (preferred, from list_sites) or a domain, e.g. example.com — scheme, www. and path are ignored when matching. If several sites share the domain the call fails and lists their site_ids…

### `get_tracking_snippet` (~137 tokens)

The script tag to install on a site, and the url it loads. Response: {"site_id":123,"type":"default","script_url":"https://...","snippet":"<script ...></script>"}. Install snippet verbatim; do not rebuild a tag from script_url. A hobby site's snippet also carries data-id, which is the only place the counter in its bundle reads the site id. Read-only: it reports the code, it does not install or verify anything.

Input parameters:

- `site` (string|integer, required): site_id from list_sites.
- `type` (string): Optional bundle variant; omit for the default script.

### `get_site_filters` (~122 tokens)

Who gets counted on a site, and who may look at the stats. Response: {"site_id":123,"hostnames":{"allowed":[],"blocked":[]},"blocked_ips":["1.2.3.4"],"countries":{"allowed":[{"code":"UA","created_at":"RFC3339"}],"blocked":[]},"public_dashboard":false}. An empty allowed list means "no restriction", not "nothing allowed". public_dashboard true means the stats are readable by anyone with the link.

Input parameters:

- `site` (string|integer, required): site_id from list_sites.

### `get_subscription` (~112 tokens)

The account's plan state — not a site's. Response: {"status":"trialing"|"active"|"past_due"|"expired"|"trial_expired"|"none","is_trial":true,"ends_at":"RFC3339","only_hobby":false}. ends_at is when the CURRENT state stops being true (trial end while trialing, period end otherwise) and is omitted when unknown. status "none" with only_hobby true means a free account, not a missing one. Takes no arguments.

### `create_site` (~178 tokens)

Add a site to this account and get back its id and tracking code. Response: {"site_id":123,"name":"https://example.com","timezone":"Europe/Amsterdam",...}. The url must include the scheme. A url this account already has is REFUSED (site_exists) rather than returned — two sites collecting the same traffic is worse than an error. Retrying with the same arguments replays the first result instead of creating a second site. Follow with get_tracking_snippet to obtain the script tag to install.

Input parameters:

- `hobby` (boolean): Optional. Request the free hobby tier; only certain domains qualify.
- `timezone` (string): Optional IANA name, e.g. "Europe/Amsterdam". Defaults to the account's.
- `url` (string, required): Full origin including scheme, e.g. "https://example.com".

### `update_site` (~102 tokens)

Change a site's url, timezone or week start. Omitted fields are left alone. Returns the updated site. Changing the url to one this account already has is refused (site_exists).

Input parameters:

- `site` (string|integer, required): site_id from list_sites.
- `timezone` (string): Optional IANA name.
- `url` (string): Optional. Full origin including scheme.
- `week_start` (integer): Optional. 0 = Sunday ... 6 = Saturday.

### `create_goal` (~192 tokens)

Add a goal to a site. A goal is EITHER a custom event (event_name), OR a page (path with operator), OR a scroll depth — give one of the three, not several. operator: "e" exact, "b" begins with, "c" contains. A duplicate name is refused (goal_exists).

Input parameters:

- `event_name` (string): Custom event to count, e.g. "Signup". Use list_prop_keys or top_custom_events to see what the site already sends.
- `name` (string, required): Shown in reports, e.g. "Signup".
- `operator` (string): How path is matched: e exact, b begins with, c contains.
- `path` (string): Page path, e.g. "/thanks". Pair with operator.
- `scroll_depth` (integer): Percent scrolled.
- `site` (string|integer, required): site_id from list_sites.

### `update_goal` (~97 tokens)

Replace a goal's definition. Send the whole goal, not just the changed fields — omitted fields are cleared, not kept.

Input parameters:

- `event_name` (string)
- `goal_id` (integer, required): id from list_goals.
- `name` (string, required)
- `operator` (string)
- `path` (string)
- `scroll_depth` (integer)
- `site` (string|integer, required): site_id from list_sites.

### `create_funnel` (~150 tokens)

Add a funnel: an ordered list of 2+ steps. Each step is one of {"type":"page","value":"/pricing"}, {"type":"event","value":"Signup"}, {"type":"entry_page"|"exit_page","value":"/"}. An exit_page step must be last. scope "visitor" (default) or "session". A duplicate name is refused (funnel_exists). Read the result with funnel_report.

Input parameters:

- `name` (string, required)
- `scope` (string)
- `site` (string|integer, required): site_id from list_sites.
- `steps` (array, required)
- `strict_order` (boolean): Steps must occur in exactly this order with nothing between.

### `update_funnel` (~87 tokens)

Replace a funnel's definition. Send the whole funnel including every step — omitted steps are removed, not kept.

Input parameters:

- `funnel_id` (integer, required): id from list_funnels.
- `name` (string, required)
- `scope` (string)
- `site` (string|integer, required): site_id from list_sites.
- `steps` (array, required)
- `strict_order` (boolean)

### `get_tracking_settings` (~138 tokens)

What the installed script actually does: which tracking features are on, which exist, and what each costs in bytes. Response: {"site_id":123,"version":N,"bundle":"...","enabled":["hash","outbound"],"features":[{"id":"outbound","label":"...","enabled":true,"locked":false,"default":false,"requires":[...],"size_br":123}]}. Locked features cannot be changed; `requires` lists features that must be on for this one to work. Needs the same access as changing them (see update_tracking_settings).

Input parameters:

- `site` (string|integer, required): site_id from list_sites.

### `update_tracking_settings` (~118 tokens)

Set which tracking features the site's script includes. REPLACES the whole selection: send every feature you want enabled, not just the new one — anything omitted is turned off. Call get_tracking_settings first for the valid ids. Rebuilds and republishes the script, so the change reaches visitors after the CDN cache clears.

Input parameters:

- `features` (array, required): Feature ids to enable, from get_tracking_settings. The complete list, not a delta; [] disables every optional feature.
- `site` (string|integer, required): site_id from list_sites.

### `update_site_filters` (~217 tokens)

Change who gets counted, and who may look. Send only the sections you want to change — an omitted section is left untouched. A section you DO send replaces that setting entirely: {"countries":{"blocked":["RU"]}} also clears the country allow list, and {"blocked_ips":[]} empties the blocklist. Read the current state with get_site_filters and send it back with your edit applied. Filtering takes effect on new traffic; it does not remove data already collected. Answers with the resulting state plus "updated":["hostnames",...] naming what changed.

Input parameters:

- `blocked_ips` (array): Replaces the IP blocklist.
- `countries` (object): Replaces the country lists. ISO 3166-1 alpha-2 codes, e.g. "UA".
- `hostnames` (object): Replaces the hostname lists. Allowed non-empty = count only these.
- `public_dashboard` (boolean): true makes the stats readable by anyone with the link.
- `site` (string|integer, required): site_id from list_sites.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-statable-analytics/statable-mcp#diagnostics

## Score history

- 2026-09-24: 78
- 2026-09-23: 78
- 2026-09-22: 77
- 2026-09-21: 77
- 2026-09-20: 76
- 2026-09-19: 76
- 2026-09-18: 75
- 2026-09-17: 75
- 2026-09-16: 74
- 2026-09-15: 74
- 2026-09-14: 73
- 2026-09-13: 73
- 2026-09-12: 72
- 2026-09-11: 72
- 2026-09-10: 69
- 2026-09-09: 69
- 2026-09-08: 69
- 2026-09-07: 69
- 2026-09-06: 69
- 2026-09-05: 69
- 2026-09-04: 54

## Common questions

### What is the Statable MCP server?

Statable is an MCP server listed in the public MCP registry as com.statable/analytics. Privacy-first, cookieless web analytics: traffic, sources, pages, goals, funnels and site setup. This page covers its npm package (@statable/mcp).

### Is the Statable MCP server safe to use?

Statable scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. 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.

### What tools does the Statable MCP server expose?

Statable exposes 25 tools: list_sites, query_stats, top_pages, top_sources, top_countries, and 20 more. Their descriptions and schemas cost roughly 4,444 tokens of context every time the server is loaded.

### Is the Statable MCP server still maintained?

Statable is still listed as active in the MCP registry. We last reached this channel on 24 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 Statable MCP server under?

Statable declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@statable/mcp
- Socket report: https://socket.dev/npm/package/@statable/mcp
- Repository: https://github.com/key-arg/statable-mcp
- Website: https://statable.com/docs/integrations/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-statable-analytics/statable-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-statable-analytics/statable-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-statable-analytics/statable-mcp