# Plausible (npm · @pipeworx/mcp-plausible)

MCP server for plausible

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-plausible/plausible-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-plausible/plausible-mcp)
- npm · `@pipeworx/mcp-plausible`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-plausible/pipeworx-mcp-plausible.md), [page](https://verifymcp.io/servers/pipeworx-io-plausible/pipeworx-mcp-plausible)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-plausible`
- Version: `0.2.1`
- 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-11-05.

- **Supply Chain Security**: 100/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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-plausible).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 640 tokens (~160/item across 4 items; 4 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Plausible MCP server?

Plausible runs locally as an npm package, launched with npx -y @pipeworx/mcp-plausible. 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 pipeworx-io-plausible -- npx -y @pipeworx/mcp-plausible
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-plausible": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-plausible"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-plausible": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-plausible"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-plausible -- npx -y @pipeworx/mcp-plausible
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-plausible --command npx --arg -y --arg @pipeworx/mcp-plausible
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-plausible:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-plausible"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-plausible": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-plausible"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-plausible -t stdio -c npx -a -y @pipeworx/mcp-plausible
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-plausible": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-plausible"
      ]
    }
  }
}
```

## 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-11-05 (score 82, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-04 (score 67, −12)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.20
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-03 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-02 (score 79, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (4)

### `plausible_overview` (~143 tokens)

Return aggregate visitors, visits, pageviews, bounce rate, visit duration, and optional goal revenue for a Plausible site. Answers how much traffic and engagement the site generated during a period.

Input parameters:

- `_apiKey` (string, required): Plausible Stats API key
- `date_range` (required): Plausible date range preset or a two-item ISO date array
- `goal` (string): Limit metrics to one configured goal display name
- `include_revenue` (boolean): Include total_revenue and average_revenue; use with a revenue goal filter
- `site_id` (string, required): Plausible site ID, usually the configured domain such as example.com

### `plausible_timeseries` (~157 tokens)

Return bounded Plausible metrics grouped by day, week, month, or hour. Answers when traffic, engagement, conversions, or revenue changed during a period.

Input parameters:

- `_apiKey` (string, required): Plausible Stats API key
- `date_range` (required): Plausible date range preset or a two-item ISO date array
- `goal` (string): Limit metrics to one configured goal display name
- `interval` (string, required): Time bucket
- `limit` (number): Maximum rows, default 100 and maximum 500
- `metrics` (array): Plausible metric names; defaults to visitors and pageviews
- `site_id` (string, required): Plausible site ID, usually the configured domain such as example.com

### `plausible_breakdown` (~173 tokens)

Return ranked Plausible metrics grouped by a page, source, campaign, geography, device, browser, or custom-property dimension. Answers which channels, content, audiences, or experiences drove results.

Input parameters:

- `_apiKey` (string, required): Plausible Stats API key
- `date_range` (required): Plausible date range preset or a two-item ISO date array
- `dimension` (string, required): Plausible dimension such as visit:source, visit:utm_campaign, event:page, visit:country_name, or event:props:plan
- `limit` (number): Maximum rows, default 20 and maximum 100
- `metrics` (array): Metrics; defaults to visitors and pageviews
- `site_id` (string, required): Plausible site ID, usually the configured domain such as example.com

### `plausible_goal_performance` (~115 tokens)

Return events, visitors, and conversion rate grouped by configured Plausible goal. Answers which signup, activation, purchase, or other goals converted during a period.

Input parameters:

- `_apiKey` (string, required): Plausible Stats API key
- `date_range` (required): Plausible date range preset or a two-item ISO date array
- `limit` (number): Maximum goals, default 20 and maximum 100
- `site_id` (string, required): Plausible site ID, usually the configured domain such as example.com

## Diagnostics

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

## Score history

- 2026-11-05: 82
- 2026-11-04: 67
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Plausible MCP server?

Plausible is an MCP server listed in the public MCP registry as io.github.pipeworx-io/plausible. MCP server for plausible. This page covers its npm package (@pipeworx/mcp-plausible).

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

Plausible scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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.

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

Plausible exposes 4 tools: plausible_overview, plausible_timeseries, plausible_breakdown, plausible_goal_performance. Their descriptions and schemas cost roughly 588 tokens of context every time the server is loaded.

### Is the Plausible MCP server still maintained?

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

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

### What did VerifyMCP test on the Plausible MCP server?

VerifyMCP ran 16 checks on Plausible, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-plausible
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-plausible
- Repository: https://github.com/pipeworx-io/mcp-plausible
- Website: https://pipeworx.io/packs/plausible
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-plausible/pipeworx-mcp-plausible.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-plausible/pipeworx-mcp-plausible/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-plausible/pipeworx-mcp-plausible.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-plausible/pipeworx-mcp-plausible