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.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
163 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 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 completed163 ms
2 days agoHandshake completed179 ms
5 days agoHandshake completed235 ms
7 days agoHandshake completed156 ms
9 days agoHandshake completed222 ms
11 days agoHandshake completed958 ms
13 days agoHandshake completed179 ms
15 days agoHandshake completed166 ms
17 days agoHandshake completed204 ms
19 days agoHandshake completed845 ms
20 days agoHandshake completed875 ms
21 days agoHandshake completed191 ms
23 days agoHandshake completed225 ms

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

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.