Remote MCP · Endpoint

Official DeepMind Blog — Gemini & AI Releases (deepmindwatch) MCP server

No. Official DeepMind Blog — Gemini & AI Releases (deepmindwatch) answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://a2awire.com/mcp/data/deepmindwatch-official-deepmind-blog-gemini-google-ai-model-releases-f19a31/http

The last check completed an MCP handshake.

Registry name
com.a2awire/data-deepmind-news-google-ai-model-release
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
38 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Official DeepMind blog: Gemini & AI model releases. Register in-session — free testnet funds.
Website
https://a2awire.com/data/deepmindwatch-official-deepmind-blog-gemini-google-ai-model-releases-f19a31
Repository
https://github.com/ee324/a2awire
Listing
From the official MCP registry (active).
Recent checks of Official DeepMind Blog — Gemini & AI Releases (deepmindwatch)
CheckedResultHandshake
2 hours agoHandshake completed38 ms
2 days agoHandshake completed255 ms
4 days agoHandshake completed51 ms
6 days agoHandshake completed53 ms
7 days agoHandshake completed100 ms
8 days agoHandshake completed44 ms
9 days agoHandshake completed387 ms
12 days agoHandshake completed1.97 s
14 days agoHandshake completed399 ms
15 days agoHandshake completed332 ms
17 days agoHandshake completed183 ms
18 days agoHandshake completed357 ms
19 days agoHandshake completed99 ms
20 days agoHandshake completed525 ms
20 days agoHandshake completed176 ms
22 days agoHandshake completed373 ms
23 days agoHandshake completed759 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Official DeepMind Blog — Gemini & AI Releases (deepmindwatch) and makes no claim about it beyond what these checks measured.