Remote MCP · Endpoint

AppScreenStudio MCP server

No. AppScreenStudio answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://www.appscreenstudio.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.appscreenstudio/app-screen-studio
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
503 ms
Tools exposed
49 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Design App Store and Google Play screenshots with your AI agent in the AppScreenStudio editor.
Listing
From the official MCP registry (active).
Recent checks of AppScreenStudio
CheckedResultHandshake
13 minutes agoHandshake completed503 ms
10 days agoHandshake completed503 ms
10 days agoHandshake completed502 ms
11 days agoHandshake completed515 ms
13 days agoHandshake completed507 ms
14 days agoHandshake completed497 ms
14 days agoHandshake completed476 ms
15 days agoHandshake completed579 ms
17 days agoHandshake completed491 ms
19 days agoHandshake completed3.42 s
21 days agoHandshake completed468 ms
24 days agoHandshake completed502 ms
26 days agoHandshake completed874 ms
28 days agoCredentials required—

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

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