Simple Analytics MCP by usefulapi
REMOTE · SIMPLE-ANALYTICS.USEFULAPI.IO
Read Simple Analytics stats: pageviews, visitors, pages, referrers, events and data exports.
Available components
Last scanned (6 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Data and Analytics
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. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability73
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 16 Oct 26 +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.
- 14 Oct 26 +4
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 58
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 17 Oct 2026 · Probed https://simple-analytics.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of simple-analytics.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://simple-analytics.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://simple-analytics.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://simple-analytics.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://simple-analytics.usefulapi.io/mcp |
| Authorisation server | https://simple-analytics.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://simple-analytics.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/simple-analytics/ |
| http (plaintext) | http://simple-analytics.usefulapi.io/mcp | Inconclusive | 302 | http://simple-analytics.usefulapi.io/mcp |
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 →
simpleanalytics_export_datapoints Export raw data points ~430
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.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | 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 | yes | 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 | yes | Start date (see description). |
| timezone | string | – | IANA time zone, e.g. Europe/Amsterdam. Default: the website setting. |
| type | string | – | Page views (default) or events. |
No output schema declared.
No examples provided.
simpleanalytics_get_breakdown Get top pages, referrers, countries or devices ~438
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>.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | What to break the traffic down by. |
| end | string | – | End date (inclusive): YYYY-MM-DD, today, yesterday or today-1d. Default: today. |
| hostname | string | yes | 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. |
No output schema declared.
No examples provided.
simpleanalytics_get_events Get event counts ~388
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=...
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
simpleanalytics_get_stats Get traffic summary ~390
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
simpleanalytics_get_timeseries Get traffic over time ~396
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
simpleanalytics_list_websites List websites ~42
List the websites of the Simple Analytics account (hostnames to use in the other tools). Good first call. Admin API: GET /api/websites.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · simple-analytics.usefulapi.io
claude mcp add --transport http io-usefulapi-simple-analytics 'https://simple-analytics.usefulapi.io/mcp'
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.