Plausible
NPM · @PIPEWORX/MCP-PLAUSIBLE · 2 COMPONENTS
MCP server for plausible
Available components
Last scanned (14 hours ago)
Scores higher than 72% of npm servers
Category Data and Analytics
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 → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-plausible). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- 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. 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −12
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.20 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 3 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 29 Oct 26 79
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-plausible@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-plausible |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-plausible/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3685302953 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:01d09844247940f81f646701920471311de8f0a73a6cd7362caa83de7e99e99eba69b3bb91f88911d9e5fc37056fec0fe87be6a678c2d3088712ac6d3 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
plausible_breakdown ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Plausible Stats API key |
| date_range | – | yes | Plausible date range preset or a two-item ISO date array |
| dimension | string | yes | 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 | yes | Plausible site ID, usually the configured domain such as example.com |
No output schema declared.
No examples provided.
plausible_goal_performance ~115
Return events, visitors, and conversion rate grouped by configured Plausible goal. Answers which signup, activation, purchase, or other goals converted during a period.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Plausible Stats API key |
| date_range | – | yes | Plausible date range preset or a two-item ISO date array |
| limit | number | – | Maximum goals, default 20 and maximum 100 |
| site_id | string | yes | Plausible site ID, usually the configured domain such as example.com |
No output schema declared.
No examples provided.
plausible_overview ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Plausible Stats API key |
| date_range | – | yes | 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 | yes | Plausible site ID, usually the configured domain such as example.com |
No output schema declared.
No examples provided.
plausible_timeseries ~157
Return bounded Plausible metrics grouped by day, week, month, or hour. Answers when traffic, engagement, conversions, or revenue changed during a period.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Plausible Stats API key |
| date_range | – | yes | Plausible date range preset or a two-item ISO date array |
| goal | string | – | Limit metrics to one configured goal display name |
| interval | string | yes | Time bucket |
| limit | number | – | Maximum rows, default 100 and maximum 500 |
| metrics | array | – | Plausible metric names; defaults to visitors and pageviews |
| site_id | string | yes | Plausible site ID, usually the configured domain such as example.com |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-plausible
claude mcp add pipeworx-io-plausible -- npx -y @pipeworx/mcp-plausible
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.