Remote MCP · Endpoint

amCharts 5 MCP server

No. amCharts 5 answered an MCP handshake 39 minutes ago.

UpLast checked 39 minutes ago

Server URL

https://mcp.amcharts.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.amcharts/amcharts5
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
758 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
On-demand access to amCharts 5 docs, code examples, and API reference
Listing
From the official MCP registry (active).
Recent checks of amCharts 5
CheckedResultHandshake
39 minutes agoHandshake completed758 ms
3 days agoHandshake completed1.51 s
13 days agoHandshake completed1.65 s
13 days agoHandshake completed1.45 s
15 days agoHandshake completed865 ms
16 days agoHandshake completed954 ms
17 days agoHandshake completed899 ms
18 days agoHandshake completed1.29 s
18 days agoHandshake completed938 ms
20 days agoHandshake completed1.03 s
22 days agoHandshake completed1.75 s
25 days agoHandshake completed1.00 s
27 days agoHandshake completed942 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 amCharts 5 and makes no claim about it beyond what these checks measured.