Remote MCP · Endpoint

Wounded Warriors MCP server

No. Wounded Warriors answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://warriorsfund.org/mcp

The last check completed an MCP handshake.

Registry name
org.warriorsfund/wounded-warriors
Transport
Streamable HTTP
Protocol negotiated
2025-11-25
Handshake latency
327 ms
Tools exposed
43 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Veteran resources, VA benefits help and giving details from Wounded Warriors (EIN 86-1336741)
Listing
From the official MCP registry (active).
Recent checks of Wounded Warriors
CheckedResultHandshake
4 hours agoHandshake completed327 ms
10 days agoHandshake completed93 ms
11 days agoHandshake completed89 ms
11 days agoHandshake completed175 ms
13 days agoHandshake completed104 ms
14 days agoHandshake completed83 ms
15 days agoHandshake completed85 ms
16 days agoHandshake completed38 ms
17 days agoHandshake completed72 ms
19 days agoHandshake completed129 ms
22 days agoHandshake completed230 ms
24 days agoHandshake completed102 ms
26 days agoHandshake completed93 ms
29 days agoHandshake completed207 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 Wounded Warriors and makes no claim about it beyond what these checks measured.