MCP server for Clamp—Web analytics for the agentic era, built for indie hackers and small teams shipping with AI. > "Did the /pricing redesign I shipped yesterday hurt checkout?" > "Build me a funnel from landing to first paid event and alert if CVR drops." > "Is my newsletter driving paid signups, or just vanity?" Tools for traffic, referrers, live visitors, events, revenue, session paths, and funnels. Query the data, build new funnels, create alerts. Pair with our [analytics skills](https://clamp.sh/docs/skills) for senior-analyst interpretation: MECE hypothesis trees, fingerprints for tracking regressions, and benchmarks calibrated to your business.

MCP readiness

D · 44/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here D, 32.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	0/10	Handshake needs credentials (HTTP 401); not readable anonymously.
Live MCP endpoint	14/25	Endpoint requires authentication or payment (4637 ms); slow response -1.
Protocol revision	0/10	No protocol revision reported by initialize.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	30/30 probes succeeded over 30 days (100%).
Tool declaration	0/10	No tools listed by tools/list.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Slow (4637 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,021 reachable MCP servers in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.

Readiness: Higher than 22% of peers; This listing 44 · peer median 81
Latency: Faster than 8% of peers; This listing 991 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Live MCP endpoint −11 — Answer initialize and tools/list at the declared endpoint.
Now: Endpoint requires authentication or payment (4637 ms); slow response -1.
Valid MCP handshake −10 — Complete the MCP handshake without errors.
Now: Handshake needs credentials (HTTP 401); not readable anonymously.
Protocol revision −10 — Support the current protocol revision.
Now: No protocol revision reported by initialize.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-06-04 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/clamp/analytics/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/clamp/analytics/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://clamp.sh/docs/mcp

Listed at (smithery)

https://clamp.sh/docs/mcp