Remote MCP · Endpoint

Dreamlit MCP server

No. Dreamlit answered an MCP handshake 10 hours ago.

UpLast checked 10 hours ago

Server URL

https://mcp.dreamlit.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.dreamlit/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
71 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Create, test, publish, and manage Dreamlit notification workflows from AI clients.
Listing
From the official MCP registry (active).
Recent checks of Dreamlit
CheckedResultHandshake
10 hours agoHandshake completed71 ms
2 days agoHandshake completed49 ms
4 days agoHandshake completed191 ms
5 days agoHandshake completed191 ms
7 days agoHandshake completed37 ms
8 days agoHandshake completed78 ms
9 days agoHandshake completed42 ms
12 days agoHandshake completed61 ms
13 days agoHandshake completed39 ms
15 days agoHandshake completed82 ms
16 days agoHandshake completed38 ms
17 days agoHandshake completed34 ms
18 days agoHandshake completed46 ms
19 days agoHandshake completed46 ms
20 days agoHandshake completed44 ms
21 days agoHandshake completed37 ms
23 days agoHandshake completed50 ms

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

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