Remote MCP · Endpoint

ai.creationloop/creationloop MCP server

No. ai.creationloop/creationloop answered an MCP handshake 51 minutes ago.

UpLast checked 51 minutes ago

Server URL

https://creationloop.ai/api/mcp

The last check completed an MCP handshake.

Registry name
ai.creationloop/creationloop
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
145 ms
Tools exposed
4 tools
Uptime, last 30 days
61.1% from 18 checks
Described by its publisher as
CreationLoop is your Marketing Agent. Read the overview, offer, and FAQ; apply as a design partner.
Listing
From the official MCP registry (active).
Recent checks of ai.creationloop/creationloop
CheckedResultHandshake
51 minutes agoHandshake completed145 ms
2 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
8 days agoFailed - the server returned an HTTP error—
9 days agoFailed - the server returned an HTTP error—
11 days agoFailed - the server returned an HTTP error—
13 days agoHandshake completed108 ms
15 days agoHandshake completed110 ms
17 days agoHandshake completed100 ms
18 days agoHandshake completed92 ms
19 days agoHandshake completed140 ms
20 days agoHandshake completed56 ms
21 days agoHandshake completed94 ms
21 days agoHandshake completed55 ms
23 days agoHandshake completed52 ms
24 days agoHandshake completed138 ms

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

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 ai.creationloop/creationloop and makes no claim about it beyond what these checks measured.