Remote MCP · Endpoint

com.googleapis.firestore/mcp MCP server

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

UpLast checked 1 hour ago

Server URL

https://firestore.googleapis.com/mcp

The last check completed an MCP handshake.

Registry name
com.googleapis.firestore/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
121 ms
Tools exposed
23 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Interact with your Google Cloud Firestore resources using natural language commands.
Listing
From the official MCP registry (active).
Recent checks of com.googleapis.firestore/mcp
CheckedResultHandshake
1 hour agoHandshake completed121 ms
18 hours agoHandshake completed160 ms
2 days agoHandshake completed123 ms
3 days agoHandshake completed110 ms
4 days agoHandshake completed407 ms
5 days agoHandshake completed117 ms
6 days agoHandshake completed108 ms
7 days agoHandshake completed116 ms
10 days agoHandshake completed111 ms
13 days agoHandshake completed106 ms
15 days agoHandshake completed105 ms
17 days agoHandshake completed105 ms
19 days agoHandshake completed105 ms
21 days agoHandshake completed108 ms
23 days agoHandshake completed107 ms
25 days agoHandshake completed111 ms
27 days agoHandshake completed98 ms
28 days agoHandshake completed120 ms
29 days agoHandshake completed630 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.firestore/mcp and makes no claim about it beyond what these checks measured.