Remote MCP · Endpoint

AstroWay Reports MCP server

No. AstroWay Reports answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
171 ms
Tools exposed
42 tools
Uptime, last 30 days
76.9% 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
1 hour agoHandshake completed171 ms
2 days agoHandshake completed223 ms
5 days agoHandshake completed121 ms
7 days agoHandshake completed163 ms
10 days agoHandshake completed123 ms
11 days agoHandshake completed168 ms
14 days agoHandshake completed128 ms
16 days agoHandshake completed150 ms
18 days agoFailed - the check failed for an unclassified reason—
19 days agoHandshake completed122 ms
21 days agoHandshake completed154 ms
22 days agoFailed - the check failed for an unclassified reason—
23 days agoFailed - the check failed for an unclassified reason—

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 10 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 AstroWay Reports and makes no claim about it beyond what these checks measured.