Remote MCP · Endpoint

AstraNL Crossing MCP server

No. AstraNL Crossing answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://verify.astranl.com/mcp/streamable

The last check completed an MCP handshake.

Registry name
com.astranl/crossing
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
275 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Look before work, claim it, check a spend, mark the outcome. For agents sharing tasks. No key.
Listing
From the official MCP registry (active).
Recent checks of AstraNL Crossing
CheckedResultHandshake
1 hour agoHandshake completed275 ms
2 days agoHandshake completed283 ms
5 days agoHandshake completed272 ms
7 days agoHandshake completed281 ms
9 days agoHandshake completed272 ms
11 days agoHandshake completed270 ms
13 days agoHandshake completed283 ms
15 days agoHandshake completed276 ms
17 days agoHandshake completed271 ms
19 days agoHandshake completed269 ms
20 days agoHandshake completed268 ms
21 days agoHandshake completed271 ms
23 days agoHandshake completed272 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 AstraNL Crossing and makes no claim about it beyond what these checks measured.