Remote MCP · Endpoint

Spoolis MCP server

No. Spoolis answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://spoolis.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.spoolis/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
124 ms
Tools exposed
32 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Verify AI work against criteria and get signed receipts. From Spoolis, guarantees for AI work.
Listing
From the official MCP registry (active).
Recent checks of Spoolis
CheckedResultHandshake
9 hours agoHandshake completed124 ms
2 days agoHandshake completed138 ms
4 days agoHandshake completed216 ms
5 days agoHandshake completed300 ms
7 days agoHandshake completed894 ms
8 days agoHandshake completed146 ms
9 days agoHandshake completed168 ms
12 days agoHandshake completed105 ms
13 days agoHandshake completed416 ms
15 days agoHandshake completed124 ms
16 days agoHandshake completed877 ms
17 days agoHandshake completed138 ms
19 days agoHandshake completed416 ms
19 days agoHandshake completed119 ms
20 days agoHandshake completed250 ms
21 days agoHandshake completed123 ms
22 days agoHandshake completed324 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 Spoolis and makes no claim about it beyond what these checks measured.