# Simple Analytics MCP by usefulapi (remote · simple-analytics.usefulapi.io)

Read Simple Analytics stats: pageviews, visitors, pages, referrers, events and data exports.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `simple-analytics.usefulapi.io`: 63/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-simple-analytics/simple-analytics.md), [page](https://verifymcp.io/servers/io-usefulapi-simple-analytics/simple-analytics)

## Channel facts

- Endpoint: `https://simple-analytics.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-10-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 73/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2293 tokens (~382/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Simple Analytics MCP by usefulapi server?

Simple Analytics MCP by usefulapi is a hosted endpoint at https://simple-analytics.usefulapi.io/mcp, so there is nothing to install locally. 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 --transport http io-usefulapi-simple-analytics 'https://simple-analytics.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-simple-analytics": {
      "url": "https://simple-analytics.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-simple-analytics": {
      "type": "http",
      "url": "https://simple-analytics.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-simple-analytics]
url = "https://simple-analytics.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-simple-analytics": {
      "type": "remote",
      "url": "https://simple-analytics.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-simple-analytics --url 'https://simple-analytics.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-simple-analytics:
    url: "https://simple-analytics.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-simple-analytics": {
      "Transport": "http",
      "Url": "https://simple-analytics.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-simple-analytics -t streamable-http -u 'https://simple-analytics.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-simple-analytics": {
      "type": "http",
      "url": "https://simple-analytics.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-10-16 (score 63, +1)

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

### 2026-10-14 (score 62, +4)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-13 (score 58, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 58)

First indexed and scored.

## MCP tools (6)

### `simpleanalytics_list_websites` (~42 tokens)

List websites

List the websites of the Simple Analytics account (hostnames to use in the other tools). Good first call. Admin API: GET /api/websites.

### `simpleanalytics_get_stats` (~390 tokens)

Get traffic summary

Aggregated traffic for one website and date range: total pageviews, unique visitors and the median seconds on page. Optional filters narrow it to a page, country, referrer, UTM value, browser, OS, device or metadata value. Stats API: GET /<hostname>.json.

Input parameters:

- `browser_name` (string): Only this browser name (Chrome).
- `country` (string): Only this country, 2-letter code (NL).
- `device_type` (string): Only this device type.
- `end` (string): End date (inclusive): YYYY-MM-DD, today, yesterday or today-1d. Default: today.
- `hostname` (string, required): Website hostname as shown in Simple Analytics, e.g. example.com (from simpleanalytics_list_websites).
- `metadata` (object): Exact metadata filters as {key: value}; all must match.
- `os_name` (string): Only this OS name (iOS).
- `page` (string): Only this page path, e.g. /pricing. A trailing * matches a prefix (/blog/*).
- `pages` (string): Only these page paths, comma separated (/contact,/product/*).
- `referrer` (string): Only this referrer (normalized, e.g. google.com).
- `start` (string): Start date: YYYY-MM-DD, today, yesterday or today-30d. Default: 1 month ago.
- `timezone` (string): IANA time zone, e.g. Europe/Amsterdam. Default: the website setting.
- `utm_campaign` (string): Only this UTM campaign.
- `utm_content` (string): Only this UTM content.
- `utm_medium` (string): Only this UTM medium.
- `utm_source` (string): Only this UTM source.
- `utm_term` (string): Only this UTM term.

### `simpleanalytics_get_timeseries` (~396 tokens)

Get traffic over time

Pageviews and visitors per hour, day, week, month or year for one website and date range (time series for charts and trends). Optional filters as in simpleanalytics_get_stats. Stats API: GET /<hostname>.json?fields=histogram.

Input parameters:

- `browser_name` (string): Only this browser name (Chrome).
- `country` (string): Only this country, 2-letter code (NL).
- `device_type` (string): Only this device type.
- `end` (string): End date (inclusive): YYYY-MM-DD, today, yesterday or today-1d. Default: today.
- `hostname` (string, required): Website hostname as shown in Simple Analytics, e.g. example.com (from simpleanalytics_list_websites).
- `interval` (string): Bucket size (default day).
- `metadata` (object): Exact metadata filters as {key: value}; all must match.
- `os_name` (string): Only this OS name (iOS).
- `page` (string): Only this page path, e.g. /pricing. A trailing * matches a prefix (/blog/*).
- `pages` (string): Only these page paths, comma separated (/contact,/product/*).
- `referrer` (string): Only this referrer (normalized, e.g. google.com).
- `start` (string): Start date: YYYY-MM-DD, today, yesterday or today-30d. Default: 1 month ago.
- `timezone` (string): IANA time zone, e.g. Europe/Amsterdam. Default: the website setting.
- `utm_campaign` (string): Only this UTM campaign.
- `utm_content` (string): Only this UTM content.
- `utm_medium` (string): Only this UTM medium.
- `utm_source` (string): Only this UTM source.
- `utm_term` (string): Only this UTM term.

### `simpleanalytics_get_breakdown` (~438 tokens)

Get top pages, referrers, countries or devices

Top values of one dimension for one website and date range, each with pageviews and visitors: pages, countries, referrers, UTM sources/mediums/campaigns/contents/terms, browsers, operating systems or device types. Optional filters as in simpleanalytics_get_stats. Stats API: GET /<hostname>.json?fields=<dimension>.

Input parameters:

- `browser_name` (string): Only this browser name (Chrome).
- `country` (string): Only this country, 2-letter code (NL).
- `device_type` (string): Only this device type.
- `dimension` (string, required): What to break the traffic down by.
- `end` (string): End date (inclusive): YYYY-MM-DD, today, yesterday or today-1d. Default: today.
- `hostname` (string, required): Website hostname as shown in Simple Analytics, e.g. example.com (from simpleanalytics_list_websites).
- `limit` (integer): Maximum number of values (default 20, max 1000).
- `metadata` (object): Exact metadata filters as {key: value}; all must match.
- `os_name` (string): Only this OS name (iOS).
- `page` (string): Only this page path, e.g. /pricing. A trailing * matches a prefix (/blog/*).
- `pages` (string): Only these page paths, comma separated (/contact,/product/*).
- `referrer` (string): Only this referrer (normalized, e.g. google.com).
- `start` (string): Start date: YYYY-MM-DD, today, yesterday or today-30d. Default: 1 month ago.
- `timezone` (string): IANA time zone, e.g. Europe/Amsterdam. Default: the website setting.
- `utm_campaign` (string): Only this UTM campaign.
- `utm_content` (string): Only this UTM content.
- `utm_medium` (string): Only this UTM medium.
- `utm_source` (string): Only this UTM source.
- `utm_term` (string): Only this UTM term.

### `simpleanalytics_get_events` (~388 tokens)

Get event counts

How often custom events happened on one website in a date range. Pass event names, or leave names out for all events (up to 1000). Stats API: GET /<hostname>.json?events=...

Input parameters:

- `browser_name` (string): Only this browser name (Chrome).
- `country` (string): Only this country, 2-letter code (NL).
- `device_type` (string): Only this device type.
- `end` (string): End date (inclusive): YYYY-MM-DD, today, yesterday or today-1d. Default: today.
- `hostname` (string, required): Website hostname as shown in Simple Analytics, e.g. example.com (from simpleanalytics_list_websites).
- `metadata` (object): Exact metadata filters as {key: value}; all must match.
- `names` (array): Event names; default all events.
- `os_name` (string): Only this OS name (iOS).
- `page` (string): Only this page path, e.g. /pricing. A trailing * matches a prefix (/blog/*).
- `pages` (string): Only these page paths, comma separated (/contact,/product/*).
- `referrer` (string): Only this referrer (normalized, e.g. google.com).
- `start` (string): Start date: YYYY-MM-DD, today, yesterday or today-30d. Default: 1 month ago.
- `timezone` (string): IANA time zone, e.g. Europe/Amsterdam. Default: the website setting.
- `utm_campaign` (string): Only this UTM campaign.
- `utm_content` (string): Only this UTM content.
- `utm_medium` (string): Only this UTM medium.
- `utm_source` (string): Only this UTM source.
- `utm_term` (string): Only this UTM term.

### `simpleanalytics_export_datapoints` (~430 tokens)

Export raw data points

Raw, unsampled page views or events of one website for a date range, as rows with only the fields asked for. The reply is capped at max_rows (default 100, max 1000) rows and 2 MB; "truncated" says more exist, so narrow the range. Rows are cut to about 40 000 characters of JSON. Dates: YYYY-MM-DD, or YYYY-MM-DDTHH for one hour (start and end the same day). Robots are left out unless asked. Needs the user id too. Export API: GET /api/export/datapoints.

Input parameters:

- `end` (string, required): End date, inclusive.
- `fields` (array): Fields to export (default added_iso, path, country_code, device_type, document_referrer). All: added_date, added_iso, added_unix, browser_name, browser_version, country_code, datapoint, device_type,…
- `hostname` (string, required): Website hostname as shown in Simple Analytics, e.g. example.com (from simpleanalytics_list_websites).
- `include_robots` (boolean): Include robot/crawler traffic (default false).
- `max_rows` (integer): Maximum rows returned (default 100).
- `start` (string, required): Start date (see description).
- `timezone` (string): IANA time zone, e.g. Europe/Amsterdam. Default: the website setting.
- `type` (string): Page views (default) or events.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-simple-analytics/simple-analytics#diagnostics

## Score history

- 2026-10-17: 63
- 2026-10-16: 63
- 2026-10-15: 62
- 2026-10-14: 62
- 2026-10-13: 58
- 2026-10-12: 58

## Common questions

### What is the Simple Analytics MCP by usefulapi server?

Simple Analytics MCP by usefulapi is listed in the public MCP registry as io.usefulapi/simple-analytics. Read Simple Analytics stats: pageviews, visitors, pages, referrers, events and data exports. This page covers its hosted endpoint (https://simple-analytics.usefulapi.io/mcp).

### Is the Simple Analytics MCP by usefulapi server safe to use?

Simple Analytics MCP by usefulapi scores 63 out of 100 on VerifyMCP. 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 Simple Analytics MCP by usefulapi server expose?

Simple Analytics MCP by usefulapi exposes 6 tools: simpleanalytics_list_websites, simpleanalytics_get_stats, simpleanalytics_get_timeseries, simpleanalytics_get_breakdown, simpleanalytics_get_events, simpleanalytics_export_datapoints. Their descriptions and schemas cost roughly 2,084 tokens of context every time the server is loaded.

### Does the Simple Analytics MCP by usefulapi server require authentication?

Yes. Simple Analytics MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Simple Analytics MCP by usefulapi server still maintained?

Simple Analytics MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://simple-analytics.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/simple-analytics/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-simple-analytics/simple-analytics.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-simple-analytics/simple-analytics.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-simple-analytics/simple-analytics