mcpbeat Sign in

Nexly Analytics MCP Server

answering

Nexly Analytics is answering right now. Last checked 2 min ago.

Read-only access to your Nexly web analytics: traffic, pages, acquisition, events, and reports.

Uptime history 51 days of history · worst day 92%
51 days agonow
93.4%
Uptime 24h
85 of 91 checks
Tools
hidden behind auth
197 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nexly Analytics does not always answer

Over the last week it answered 98.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add analytics --transport http https://api.nexly.to/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "analytics": {
      "url": "https://api.nexly.to/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.analytics]
url = "https://api.nexly.to/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "analytics": {
      "url": "https://api.nexly.to/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "analytics": {
      "url": "https://api.nexly.to/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://api.nexly.to/mcp streamable-http sign-in 185 ms 2 min ago

Alternatives to Nexly Analytics

same job, measured the same way
SEO Tools: Google Analytics 4
by antohins

Google Analytics 4: reports, traffic sources, landing pages, events, realtime (read-only).

32 installs/wk local only
DevDome Analytics
by devdome

Website traffic, bot reports, realtime visitors and site health for your DevDome sites

10 tools answering
Codemouse
by squidcode

Read-only access to your CodeMouse accounts, repositories, and AI pull-request reviews.

answering
Toffu
by toffu

AI marketing platform your agent runs end to end: ads, analytics, content, and reports.

answering
Umami
by mikusnuz

MCP server for Umami Analytics API v2 — websites, stats, events, reports, and realtime

72 installs/wk local only
Vortex Iq
by vortexiq

Read-only access to your VortexIQ store data: audits, KPIs, alerts, Brand DNA, reports, Ask VIQ.

answering
Decaframe
by decaframe

Presentations, slides, reports and one-pagers your agent designs and you edit. Exports to one file.

108 installs/wk local only
ProvenTools
by proventools

Read-only ProvenTools business ideas, evidence, build prompts, and validation reports.

33 installs/wk local only

Nexly Analytics — questions

Answers built from our own checks of this server.

Why is there no tool list for Nexly Analytics?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 93.4% of checks in the last 24 hours got a reply.
Is Nexly Analytics working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 85 of 91 checks got a reply (93.4%), average response time 197 ms. The bar chart above shows every period we have measured.
How do I connect Nexly Analytics?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Nexly Analytics?
No API key is involved. Nexly Analytics answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Nexly Analytics?
It answers our handshake in 197 ms on average, which is faster than 70% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.