Remote MCP · Endpoint

AstroWay Reports MCP server

No. AstroWay Reports answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://mcp.astroway.info/mcp/reports

The last check completed an MCP handshake.

Registry name
info.astroway/reports
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
407 ms
Tools exposed
46 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Sixteen finished PDF reports and the white-label configuration behind them.
Listing
From the official MCP registry (active).
Recent checks of AstroWay Reports
CheckedResultHandshake
44 minutes agoHandshake completed407 ms
3 days agoHandshake completed612 ms
12 days agoHandshake completed361 ms
13 days agoFailed - the check failed for an unclassified reason—
14 days agoHandshake completed140 ms
15 days agoHandshake completed196 ms
16 days agoHandshake completed326 ms
17 days agoHandshake completed147 ms
18 days agoHandshake completed410 ms
20 days agoHandshake completed171 ms
22 days agoHandshake completed223 ms
25 days agoHandshake completed121 ms
27 days agoHandshake completed163 ms

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

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