Remote MCP · Endpoint

Charts by Szum MCP server

No. Charts by Szum answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://szum.io/mcp

The last check completed an MCP handshake.

Registry name
io.szum/charts
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
294 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Create, inspect, manage, and render charts and data visualizations as SVG/PNG or interactive embeds.
Listing
From the official MCP registry (active).
Recent checks of Charts by Szum
CheckedResultHandshake
1 hour agoHandshake completed294 ms
9 days agoHandshake completed350 ms
10 days agoHandshake completed326 ms
11 days agoHandshake completed333 ms
12 days agoHandshake completed307 ms
14 days agoHandshake completed310 ms
14 days agoHandshake completed329 ms
15 days agoHandshake completed371 ms
17 days agoHandshake completed414 ms
19 days agoHandshake completed323 ms
21 days agoHandshake completed394 ms
24 days agoHandshake completed346 ms
26 days agoHandshake completed302 ms
28 days agoHandshake completed290 ms

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

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 Charts by Szum and makes no claim about it beyond what these checks measured.