Back to MCP servers

Analytics

https://analytics.worker.myoperations.click/mcp
● healthy

Visitas, páginas, origens e metas dos seus sites, sem cookies

Transport
streamable-http
Auth
—
Cost
—
Protocol revision
2025-11-25
negotiated, not declared

MCP readiness

C · 73/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 C+, 64.1/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 7/10 initialize answered; tools/list failed.
  • tools/list did not return a tools array
Live MCP endpoint 25/25 Endpoint answers the MCP initialize handshake (302 ms).
Protocol revision 8/10 Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 23/23 probes succeeded over 30 days (100%).
Tool declaration 0/10 No tools listed by tools/list.
Verified identity 7/10 Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Freshness + modern flags 4/5 seen in a source within 7 days.
Auth declaration 0/5 How to authenticate is not stated.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Responsive (302 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 35% of peers
This listing 73 · peer median 81
Latency
Faster than 70% of peers
This listing 202 ms · peer median 326 ms

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

  • Tool declaration −10 — Declare every tool with a description and input schema.
    Now: No tools listed by tools/list.
  • Auth declaration −5 — State how to authenticate (an auth scheme, or that none is needed).
    Now: How to authenticate is not stated.
  • Valid MCP handshake −3 — Complete the MCP handshake without errors.
    Now: initialize answered; tools/list failed.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

mcp-registry since 2026-10-21

How to connect

MCP endpoint (streamable-http)
https://analytics.worker.myoperations.click/mcp
JSON-RPC initialize probe
curl -X POST https://analytics.worker.myoperations.click/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://ciromaciel.click/mcp/analytics