Remote MCP · Endpoint

Official Google Product Announcements — buy per-query in-session (googleblogwatch) MCP server

No. Official Google Product Announcements — buy per-query in-session (googleblogwatch) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://a2awire.com/mcp/data/googleblogwatch-official-google-product-announcements-releases-a7837c/http

The last check completed an MCP handshake.

Registry name
com.a2awire/data-google-product-announcement-release
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
35 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Official Google product launches. $0.01/query. Register in-session — free testnet funds.
Website
https://a2awire.com/data/googleblogwatch-official-google-product-announcements-releases-a7837c
Repository
https://github.com/ee324/a2awire
Listing
From the official MCP registry (active).
Recent checks of Official Google Product Announcements — buy per-query in-session (googleblogwatch)
CheckedResultHandshake
1 hour agoHandshake completed35 ms
1 day agoHandshake completed75 ms
2 days agoHandshake completed58 ms
3 days agoHandshake completed45 ms
4 days agoHandshake completed64 ms
5 days agoHandshake completed31 ms
6 days agoHandshake completed55 ms
9 days agoHandshake completed30 ms
12 days agoHandshake completed34 ms
14 days agoHandshake completed55 ms
16 days agoHandshake completed32 ms
18 days agoHandshake completed84 ms
20 days agoHandshake completed62 ms
22 days agoHandshake completed72 ms
24 days agoHandshake completed160 ms
26 days agoHandshake completed236 ms
27 days agoHandshake completed100 ms
29 days agoHandshake completed82 ms

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

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 Google Product Announcements — buy per-query in-session (googleblogwatch) and makes no claim about it beyond what these checks measured.