Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.

MCP readiness

D · 43/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+, 60.8/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	15/25	Endpoint requires authentication or payment (130 ms).
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	7/10	Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Freshness + modern flags	0/5	not seen in a source for over 30 days.
Auth declaration	2/5	Declares credential scheme: bearer_api_key.

Applicable criteria total 90 points, scaled to 100.

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

Measured 2026-11-10.

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 52,570 reachable MCP servers in our daily snapshot (2026-11-11 14:47 UTC). Display only; it does not change search order.

Readiness: Higher than 15% of peers; This listing 43 · peer median 81
Latency: Faster than 86% of peers; This listing 130 ms · peer median 371 ms

Where it loses the most points

Valid MCP handshake −10 — Handshake needs credentials (HTTP 401); not readable anonymously.
Live MCP endpoint −10 — Endpoint requires authentication or payment (130 ms).
Protocol revision −10 — No protocol revision reported by initialize.

How many agent tools actually work · All statistics

Adoption signals

Public signals from outside this directory, shown for context. They do not change search order or grades.

GitHub: ★ 81,367 · 6,722 forks; last push 2026-11-11
Site rank (Tranco): #13,280 of the top 1M; netdata.cloud · list of 2026-11-10

Listed in

Directories this entry was found in.

chiark since 2026-06-04 pulsemcp since 2026-08-18 ↗ mcp-registry since 2026-08-18 agenstry since 2026-10-22 ↗

How to connect

MCP endpoint (streamable-http)

https://app.netdata.cloud/api/v1/mcp

JSON-RPC initialize probe

curl -X POST https://app.netdata.cloud/api/v1/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://www.netdata.cloud

Source code

https://github.com/netdata/netdata