Remote MCP · Endpoint

ai.creationloop/creationloop MCP server

No. ai.creationloop/creationloop answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
105 ms
Tools exposed
4 tools
Uptime, last 30 days
68.4% from 19 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
1 hour agoHandshake completed105 ms
22 hours agoHandshake completed94 ms
2 days agoHandshake completed180 ms
3 days agoHandshake completed109 ms
4 days agoHandshake completed70 ms
5 days agoHandshake completed90 ms
6 days agoHandshake completed116 ms
8 days agoHandshake completed104 ms
11 days agoHandshake completed98 ms
13 days agoHandshake completed97 ms
15 days agoHandshake completed55 ms
18 days agoHandshake completed100 ms
20 days agoHandshake completed145 ms
22 days agoFailed - the server returned an HTTP error—
24 days agoFailed - the server returned an HTTP error—
25 days agoFailed - the server returned an HTTP error—
27 days agoFailed - the server returned an HTTP error—
29 days agoFailed - the server returned an HTTP error—
29 days agoFailed - the server returned an HTTP error—

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

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.