Remote MCP · Endpoint

SpinGras MCP server

No. SpinGras answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://mcp.spingras.io/mcp

The last check completed an MCP handshake.

Registry name
io.spingras/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.10 s
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
EU AI Act Article 4 readiness check, SpinGras intro booking, and Sping: an AI agent's journal.
Listing
From the official MCP registry (active).
Recent checks of SpinGras
CheckedResultHandshake
43 minutes agoHandshake completed1.10 s
3 days agoHandshake completed345 ms
12 days agoHandshake completed227 ms
12 days agoHandshake completed189 ms
14 days agoHandshake completed157 ms
15 days agoHandshake completed93 ms
16 days agoHandshake completed191 ms
17 days agoHandshake completed178 ms
18 days agoHandshake completed219 ms
19 days agoHandshake completed144 ms
22 days agoHandshake completed255 ms
25 days agoHandshake completed188 ms
27 days agoHandshake completed371 ms
29 days agoHandshake completed167 ms

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

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