Pirsch Analytics MCP by usefulapi
REMOTE · PIRSCH.USEFULAPI.IO
Read Pirsch web analytics: visitors, pages, referrers, UTM, events, funnels and sessions.
Available components
Last scanned (1 hour 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 Usability69
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 18670 tokens (~691/item across 27 items; 27 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 27 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 28 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.2 → 1.1.0 functional
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 57
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://pirsch.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 pirsch.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://pirsch.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://pirsch.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://pirsch.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://pirsch.usefulapi.io/mcp |
| Authorisation server | https://pirsch.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pirsch.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/pirsch/ |
| http (plaintext) | http://pirsch.usefulapi.io/mcp | Inconclusive | 302 | http://pirsch.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 →
pirsch_list_tags List tags ~1,009
Tag keys with views and share. Use pirsch_get_tag_breakdown to see the values of one key. GET /api/v1/statistics/tags.
| Name | Type | Req | Description |
|---|---|---|---|
| browser | string | – | Browser. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| channel | string | – | Traffic channel such as "Paid Search" or "Organic Search". Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| city | string | – | City name. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| country | string | – | ISO 3166 alpha-2 country code such as jp. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| direction | string | – | Sort direction. |
| domain_id | string | yes | Pirsch domain (dashboard) id. Get it from pirsch_list_domains. |
| entry_path | string | – | Entry page path. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| event | string | – | Event name. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| event_meta | object | – | Event metadata key/value pairs; only events with all pairs match. |
| exit_path | string | – | Exit page path. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| from | string | yes | First day, yyyy-mm-dd (in the dashboard time zone unless tz is set). |
| hostname | string | – | Hostname (useful for rollup views). Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| language | string | – | ISO 639-1 language code such as en. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Results to skip (default 0). Pass the previous reply's next_offset. |
| os | string | – | Operating system. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| path | string | – | Page path, for example /pricing. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| pattern | string | – | Regular expression that filters and groups pages, for example (?i)^/blog/[^/]+$. |
| platform | string | – | Platform. |
| referrer | string | – | Referrer, usually a URL. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| referrer_name | string | – | Referrer name, usually the hostname. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| screen_class | string | – | Screen class XXL, XL, L, M or S. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| search | string | – | Only rows whose main field contains this text. |
| sort | string | – | Field to sort by, for example visitors, views, sessions or bounce_rate. |
| tag | string | – | Tag key to filter for. |
| tags | object | – | Tag key/value pairs; only results with all pairs match. |
| to | string | yes | Last day, yyyy-mm-dd, whole day included. |
| tz | string | – | IANA time zone such as Europe/Berlin. Default: the dashboard's time zone. |
| utm_campaign | string | – | UTM campaign. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| utm_content | string | – | UTM content. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| utm_medium | string | – | UTM medium. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| utm_source | string | – | UTM source. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| utm_term | string | – | UTM term. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
No output schema declared.
No examples provided.
pirsch_list_utm List UTM parameters ~1,050
Visitors per UTM source, medium, campaign, content or term. Filters narrow the data (for example country=de, path=~blog). Results are rows with visitors, views, sessions, bounces and relative shares. GET /api/v1/statistics/utm/{dimension}.
| Name | Type | Req | Description |
|---|---|---|---|
| browser | string | – | Browser. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| channel | string | – | Traffic channel such as "Paid Search" or "Organic Search". Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| city | string | – | City name. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| country | string | – | ISO 3166 alpha-2 country code such as jp. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| dimension | string | yes | Which UTM parameter to break down. |
| direction | string | – | Sort direction. |
| domain_id | string | yes | Pirsch domain (dashboard) id. Get it from pirsch_list_domains. |
| entry_path | string | – | Entry page path. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| event | string | – | Event name. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| event_meta | object | – | Event metadata key/value pairs; only events with all pairs match. |
| exit_path | string | – | Exit page path. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| from | string | yes | First day, yyyy-mm-dd (in the dashboard time zone unless tz is set). |
| hostname | string | – | Hostname (useful for rollup views). Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| language | string | – | ISO 639-1 language code such as en. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Results to skip (default 0). Pass the previous reply's next_offset. |
| os | string | – | Operating system. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| path | string | – | Page path, for example /pricing. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| pattern | string | – | Regular expression that filters and groups pages, for example (?i)^/blog/[^/]+$. |
| platform | string | – | Platform. |
| referrer | string | – | Referrer, usually a URL. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| referrer_name | string | – | Referrer name, usually the hostname. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| screen_class | string | – | Screen class XXL, XL, L, M or S. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| search | string | – | Only rows whose main field contains this text. |
| sort | string | – | Field to sort by, for example visitors, views, sessions or bounce_rate. |
| tag | string | – | Tag key to filter for. |
| tags | object | – | Tag key/value pairs; only results with all pairs match. |
| to | string | yes | Last day, yyyy-mm-dd, whole day included. |
| tz | string | – | IANA time zone such as Europe/Berlin. Default: the dashboard's time zone. |
| utm_campaign | string | – | UTM campaign. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| utm_content | string | – | UTM content. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| utm_medium | string | – | UTM medium. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| utm_source | string | – | UTM source. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
| utm_term | string | – | UTM term. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain). |
No output schema declared.
No examples provided.
How do I install the Pirsch Analytics MCP by usefulapi server?
Pirsch Analytics MCP by usefulapi is a hosted endpoint at https://pirsch.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 · pirsch.usefulapi.io
claude mcp add --transport http io-usefulapi-pirsch 'https://pirsch.usefulapi.io/mcp'
What is the Pirsch Analytics MCP by usefulapi server?
Pirsch Analytics MCP by usefulapi is listed in the public MCP registry as io.usefulapi/pirsch. Read Pirsch web analytics: visitors, pages, referrers, UTM, events, funnels and sessions. This page covers its hosted endpoint (https://pirsch.usefulapi.io/mcp).
Is the Pirsch Analytics MCP by usefulapi server safe to use?
Pirsch Analytics MCP by usefulapi scores 62 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 Pirsch Analytics MCP by usefulapi server expose?
Pirsch Analytics MCP by usefulapi exposes 27 tools: pirsch_list_domains, pirsch_get_domain, pirsch_get_overview, pirsch_get_totals, pirsch_get_visitors_time_series, and 22 more. Their descriptions and schemas cost roughly 18,454 tokens of context every time the server is loaded.
Does the Pirsch Analytics MCP by usefulapi server require authentication?
Yes. Pirsch 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 Pirsch Analytics MCP by usefulapi server still maintained?
Pirsch 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.