Analytics
pure-analytics.com
Provides MCP tools for retrieving aggregated website traffic analytics and accessing the Pure Analytics API reference.
ENDPOINT 1
https://pure-analytics.com/mcp
MCP server metadata
- Name
- pure-analytics
- Version
- 1.0.0
Pure Analytics is privacy-friendly web analytics. Call get_api_reference (no key needed) to learn the metrics, breakdown dimensions and filters. Call get_analytics to read traffic, sources, landing pages, AI-assistant referrals and revenue for the websites covered by the API key sent on this connection as the X-API-Key header (or Authorization: Bearer <key>). Every tool is read-only.
Known tools 2
get_analyticsAggregated traffic for the websites covered by the API key sent on this MCP connection (X-API-Key header).
Inferred read-onlyget_api_referencePublic reference, no API key needed: accepted metrics, breakdown dimensions, filters, granularities, limits, rate limit, error format and plan prices of Pure Analytics.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.pure-analytics]
url = "https://pure-analytics.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"pure-analytics": {
"type": "http",
"url": "https://pure-analytics.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: pure-analytics
Remote MCP URL: https://pure-analytics.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"pure-analytics": {
"url": "https://pure-analytics.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"pure-analytics": {
"type": "http",
"url": "https://pure-analytics.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "pure-analytics",
"transport": "streamable-http",
"url": "https://pure-analytics.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.