Remote MCP · Endpoint

Valor AI MCP server

No. Valor AI answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://www.tryvalor.ai/mcp/public

The last check completed an MCP handshake.

Registry name
io.github.jchacker5/valor-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
161 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free, read-only VA disability help: claims Q&A with VA.gov sources, BDD checklist, rating math.
Listing
From the official MCP registry (deprecated).
Recent checks of Valor AI
CheckedResultHandshake
5 hours agoHandshake completed161 ms
9 days agoHandshake completed396 ms
10 days agoHandshake completed182 ms
11 days agoHandshake completed1.06 s
12 days agoHandshake completed188 ms
14 days agoHandshake completed1.38 s
14 days agoHandshake completed300 ms
15 days agoHandshake completed332 ms
17 days agoHandshake completed403 ms
19 days agoHandshake completed273 ms
21 days agoHandshake completed290 ms
24 days agoHandshake completed218 ms
26 days agoHandshake completed174 ms
28 days agoHandshake completed1.49 s

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