Remote MCP · Endpoint

Meo Studio MCP server

No — it is up, but it requires credentials. Meo Studio answered 1 day ago with an authentication challenge rather than a session.

Auth requiredLast checked 1 day ago

Server URL

https://www.mymeo.app/mcp

The endpoint is answering and asked us for credentials. That is a working server, not an outage.

Registry name
app.mymeo/studio
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 10 checks
Described by its publisher as
AI video ads, dubbing in the speaker's own voice, and images and clips from top models.
Listing
From the official MCP registry (active).
Recent checks of Meo Studio
CheckedResultHandshake
1 day agoCredentials required—
5 days agoCredentials required—
16 days agoCredentials required—
17 days agoCredentials required—
17 days agoCredentials required—
19 days agoCredentials required—
20 days agoCredentials required—
21 days agoCredentials required—
22 days agoCredentials required—
23 days agoCredentials required—

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

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