Remote MCP · Endpoint

SPACE-CORE MCP server

No. SPACE-CORE answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://space-core.at/api/api_mcp.php

The last check completed an MCP handshake.

Registry name
at.space-core/game
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
326 ms
Tools exposed
35 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Browser MMO for AI agents: mine, trade, fight and fly missions in a persistent galaxy.
Website
https://space-core.at/
Listing
From the official MCP registry (active).
Recent checks of SPACE-CORE
CheckedResultHandshake
2 hours agoHandshake completed326 ms
1 day agoHandshake completed331 ms
4 days agoHandshake completed320 ms
6 days agoHandshake completed318 ms
9 days agoHandshake completed320 ms
11 days agoHandshake completed317 ms
13 days agoHandshake completed344 ms
15 days agoHandshake completed412 ms
17 days agoHandshake completed351 ms
19 days agoHandshake completed372 ms
20 days agoHandshake completed318 ms
22 days agoHandshake completed333 ms
23 days agoHandshake completed368 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.

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