Remote MCP · Endpoint

Performance Atlas MCP server

No. Performance Atlas answered an MCP handshake 58 minutes ago.

UpLast checked 58 minutes ago

Server URL

https://creatinginai.com/agents/mcp

The last check completed an MCP handshake.

Registry name
com.creatinginai/performance-atlas
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.03 s
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Acting direction for AI video and voice: state-based behaviour kits and a free prompt linter.
Listing
From the official MCP registry (active).
Recent checks of Performance Atlas
CheckedResultHandshake
58 minutes agoHandshake completed1.03 s
1 day agoHandshake completed1.61 s
4 days agoHandshake completed1.25 s
6 days agoHandshake completed1.44 s
9 days agoHandshake completed787 ms
11 days agoHandshake completed1.60 s
13 days agoHandshake completed1.25 s
15 days agoHandshake completed1.16 s
17 days agoHandshake completed1.07 s
19 days agoHandshake completed1.19 s
21 days agoHandshake completed962 ms
22 days agoHandshake completed938 ms
23 days agoHandshake completed945 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 Performance Atlas and makes no claim about it beyond what these checks measured.