Remote MCP · Endpoint

MCP Charts MCP server

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

UpLast checked 1 hour ago

Server URL

https://mcpcharts.com/mcp

The last check completed an MCP handshake.

Registry name
com.mcpcharts/mcpcharts
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
394 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Find MCP servers, skills, plugins, agents, prompts and rules for any task.
Listing
From the official MCP registry (active).
Recent checks of MCP Charts
CheckedResultHandshake
1 hour agoHandshake completed394 ms
2 days agoHandshake completed191 ms
5 days agoHandshake completed267 ms
7 days agoHandshake completed244 ms
9 days agoHandshake completed302 ms
11 days agoHandshake completed388 ms
13 days agoHandshake completed283 ms
15 days agoHandshake completed290 ms
17 days agoHandshake completed173 ms
19 days agoHandshake completed142 ms
20 days agoHandshake completed258 ms
21 days agoHandshake completed240 ms
23 days agoHandshake completed162 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 MCP Charts and makes no claim about it beyond what these checks measured.