Remote MCP · Endpoint

Launch529: 529 plans and college costs MCP server

No. Launch529: 529 plans and college costs answered an MCP handshake 6 days ago.

UpLast checked 6 days ago

Server URL

https://launch529.com/api/public/mcp

The last check completed an MCP handshake.

Registry name
com.launch529/open-data
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
168 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Compare state 529 plans, look up college costs and check qualified 529 expenses. Free, no key.
Listing
From the official MCP registry (active).
Recent checks of Launch529: 529 plans and college costs
CheckedResultHandshake
6 days agoHandshake completed168 ms
7 days agoHandshake completed247 ms
7 days agoHandshake completed202 ms
9 days agoHandshake completed172 ms
10 days agoHandshake completed220 ms
11 days agoHandshake completed170 ms
12 days agoHandshake completed251 ms
13 days agoHandshake completed216 ms
15 days agoHandshake completed208 ms
17 days agoHandshake completed189 ms
20 days agoHandshake completed239 ms
22 days agoHandshake completed245 ms
24 days agoHandshake completed299 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 Launch529: 529 plans and college costs and makes no claim about it beyond what these checks measured.