Remote MCP · Endpoint

com.googleapis.datastream/mcp MCP server

No. com.googleapis.datastream/mcp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://datastream.googleapis.com/mcp

The last check completed an MCP handshake.

Registry name
com.googleapis.datastream/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
33 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Interact with your Google Cloud Datastream resources using natural language commands.
Listing
From the official MCP registry (active).
Recent checks of com.googleapis.datastream/mcp
CheckedResultHandshake
1 hour agoHandshake completed33 ms
18 hours agoHandshake completed44 ms
2 days agoHandshake completed31 ms
3 days agoHandshake completed112 ms
4 days agoHandshake completed62 ms
5 days agoHandshake completed32 ms
6 days agoHandshake completed104 ms
7 days agoHandshake completed96 ms
10 days agoHandshake completed31 ms
13 days agoHandshake completed122 ms
15 days agoHandshake completed144 ms
17 days agoHandshake completed35 ms
19 days agoHandshake completed45 ms
21 days agoHandshake completed91 ms
23 days agoHandshake completed31 ms
25 days agoHandshake completed86 ms
27 days agoHandshake completed34 ms
28 days agoHandshake completed106 ms
29 days agoHandshake completed389 ms

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

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 com.googleapis.datastream/mcp and makes no claim about it beyond what these checks measured.