Remote MCP · Endpoint

Mimicly MCP server

No. Mimicly answered an MCP handshake 2 hours ago.

UpLast checked 2 hours 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
464 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 15 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
2 hours agoHandshake completed464 ms
1 day agoHandshake completed469 ms
4 days agoHandshake completed438 ms
6 days agoHandshake completed430 ms
8 days agoHandshake completed498 ms
9 days agoHandshake completed922 ms
11 days agoHandshake completed431 ms
12 days agoHandshake completed475 ms
13 days agoHandshake completed428 ms
16 days agoHandshake completed433 ms
17 days agoHandshake completed441 ms
19 days agoHandshake completed410 ms
20 days agoHandshake completed435 ms
21 days agoHandshake completed413 ms
22 days agoHandshake completed425 ms

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

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.