Remote MCP · Endpoint

Semantic Geometry MCP server

No. Semantic Geometry answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://verify.semgeo.cl/mcp

The last check completed an MCP handshake.

Registry name
io.github.marcoret74/semantic-geometry
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
1.10 s
Tools exposed
48 tools
Uptime, last 30 days
85.7% from 14 checks
Described by its publisher as
Deterministic verifier: LLM proposes, graph verifies. Sub-ms, offline, 0 tokens.
Listing
From the official MCP registry (active).
Recent checks of Semantic Geometry
CheckedResultHandshake
4 hours agoHandshake completed1.10 s
10 days agoHandshake completed403 ms
11 days agoHandshake completed670 ms
11 days agoFailed - the request timed out—
13 days agoHandshake completed452 ms
14 days agoHandshake completed515 ms
15 days agoHandshake completed2.88 s
16 days agoHandshake completed1.04 s
17 days agoHandshake completed461 ms
19 days agoHandshake completed1.09 s
22 days agoHandshake completed412 ms
24 days agoHandshake completed403 ms
26 days agoHandshake completed492 ms
29 days agoFailed - the request timed out—

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

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 Semantic Geometry and makes no claim about it beyond what these checks measured.