Remote MCP · Endpoint

Mimicly MCP server

No. Mimicly answered an MCP handshake 16 minutes ago.

UpLast checked 16 minutes ago

Server URL

https://mimicly.net/mcp

The last check completed an MCP handshake.

Registry name
net.mimicly/chat-mockups
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
723 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Make fictional chat mockups and text story scenes, with a preview and a link to edit in Mimicly.
Listing
From the official MCP registry (active).
Recent checks of Mimicly
CheckedResultHandshake
16 minutes agoHandshake completed723 ms
8 days agoHandshake completed463 ms
9 days agoHandshake completed444 ms
11 days agoHandshake completed430 ms
12 days agoHandshake completed506 ms
13 days agoHandshake completed619 ms
14 days agoHandshake completed574 ms
14 days agoHandshake completed472 ms
16 days agoHandshake completed423 ms
19 days agoHandshake completed420 ms
21 days agoHandshake completed517 ms
24 days agoHandshake completed510 ms
26 days agoHandshake completed464 ms
28 days agoHandshake completed469 ms

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

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