Remote MCP · Endpoint

CleanChart MCP server

No. CleanChart answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://www.cleanchart.app/api/mcp

The last check completed an MCP handshake.

Registry name
app.cleanchart/cleanchart
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.67 s
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Clean messy tabular data and render publication-ready PNG charts from your AI assistant.
Listing
From the official MCP registry (active).
Recent checks of CleanChart
CheckedResultHandshake
5 hours agoHandshake completed1.67 s
3 days agoHandshake completed161 ms
12 days agoHandshake completed290 ms
12 days agoHandshake completed131 ms
14 days agoHandshake completed1.42 s
15 days agoHandshake completed156 ms
16 days agoHandshake completed124 ms
17 days agoHandshake completed149 ms
18 days agoHandshake completed205 ms
19 days agoHandshake completed225 ms
22 days agoHandshake completed129 ms
25 days agoHandshake completed298 ms
27 days agoHandshake completed776 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with CleanChart and makes no claim about it beyond what these checks measured.