Remote MCP · Endpoint

Asrs Reports MCP server

No. Asrs Reports answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://gateway.pipeworx.io/asrs-reports/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/asrs-reports
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.05 s
Tools exposed
47 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
NASA Aviation Safety Reporting System (ASRS) — de-identified aviation safety incident narratives.
Listing
From the official MCP registry (active).
Recent checks of Asrs Reports
CheckedResultHandshake
34 minutes agoHandshake completed1.05 s
8 days agoHandshake completed1.10 s
9 days agoHandshake completed82 ms
11 days agoHandshake completed124 ms
12 days agoHandshake completed81 ms
13 days agoHandshake completed987 ms
14 days agoHandshake completed125 ms
14 days agoHandshake completed931 ms
16 days agoHandshake completed1.51 s
19 days agoHandshake completed836 ms
21 days agoHandshake completed2.53 s
24 days agoHandshake completed74 ms
26 days agoHandshake completed85 ms
28 days agoHandshake completed61 ms

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

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