Remote MCP · Endpoint

GEOMETRY MCP server

No. GEOMETRY answered an MCP handshake 11 hours ago.

UpLast checked 11 hours ago

Server URL

https://mcp.geometry.app/mcp

The last check completed an MCP handshake.

Registry name
app.geometry/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
845 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Deterministic calendars and cosmic date JSON for AI agents via MCP (Gregorian 1900-2100).
Listing
From the official MCP registry (active).
Recent checks of GEOMETRY
CheckedResultHandshake
11 hours agoHandshake completed845 ms
2 days agoHandshake completed659 ms
4 days agoHandshake completed607 ms
6 days agoHandshake completed1.11 s
7 days agoHandshake completed743 ms
8 days agoHandshake completed1.15 s
9 days agoHandshake completed911 ms
12 days agoHandshake completed307 ms
14 days agoHandshake completed406 ms
15 days agoHandshake completed689 ms
16 days agoHandshake completed580 ms
18 days agoHandshake completed716 ms
19 days agoHandshake completed695 ms
19 days agoHandshake completed778 ms
20 days agoHandshake completed289 ms
21 days agoHandshake completed785 ms
23 days agoHandshake completed334 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 GEOMETRY and makes no claim about it beyond what these checks measured.