Remote MCP · Endpoint

io.github.sntlperson/space-intelligence MCP server

No. io.github.sntlperson/space-intelligence answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp-preview.sntl.space/mcp

The last check completed an MCP handshake.

Registry name
io.github.sntlperson/space-intelligence
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
307 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Space company and market intelligence from SNTL Space.
Listing
From the official MCP registry (active).
Recent checks of io.github.sntlperson/space-intelligence
CheckedResultHandshake
1 hour agoHandshake completed307 ms
2 days agoHandshake completed219 ms
5 days agoHandshake completed262 ms
7 days agoHandshake completed299 ms
9 days agoHandshake completed342 ms
11 days agoHandshake completed547 ms
13 days agoHandshake completed271 ms
15 days agoHandshake completed165 ms
18 days agoHandshake completed356 ms
19 days agoHandshake completed642 ms
21 days agoHandshake completed196 ms
21 days agoHandshake completed176 ms
23 days agoHandshake completed282 ms
25 days agoHandshake completed373 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.

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.sntlperson/space-intelligence and makes no claim about it beyond what these checks measured.