Remote MCP · Endpoint

SpinGras MCP server

No. SpinGras answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
255 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
EU AI Act Article 4 (AI literacy) readiness check and intro booking with SpinGras, Amsterdam.
Website
https://spingras.io/
Listing
From the official MCP registry (active).
Recent checks of SpinGras
CheckedResultHandshake
1 hour agoHandshake completed255 ms
2 days agoHandshake completed188 ms
5 days agoHandshake completed371 ms
7 days agoHandshake completed167 ms
9 days agoHandshake completed140 ms
11 days agoHandshake completed196 ms
13 days agoHandshake completed152 ms
15 days agoHandshake completed133 ms
16 days agoHandshake completed174 ms
18 days agoHandshake completed169 ms
19 days agoHandshake completed398 ms
20 days agoHandshake completed302 ms
23 days agoHandshake completed244 ms
24 days agoHandshake completed287 ms

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

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