Remote MCP · Endpoint
Payload Validator MCP server
No. Payload Validator answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://payload-validator.gumballtools.com/api/mcp
The last check completed an MCP handshake.
- Registry name
- com.gumballtools/payload-validator
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 228 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Validate JSON, YAML, XML and CSV with exact line/column errors and silent-corruption warnings.
- Repository
- https://github.com/bwalvoord/gumball
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 228 ms |
| 12 hours ago | Handshake completed | 860 ms |
| 1 day ago | Handshake completed | 99 ms |
| 2 days ago | Handshake completed | 137 ms |
| 4 days ago | Handshake completed | 270 ms |
| 4 days ago | Handshake completed | 175 ms |
| 5 days ago | Handshake completed | 80 ms |
| 6 days ago | Handshake completed | 403 ms |
| 8 days ago | Handshake completed | 158 ms |
| 11 days ago | Handshake completed | 101 ms |
| 13 days ago | Handshake completed | 145 ms |
| 16 days ago | Handshake completed | 115 ms |
| 18 days ago | Handshake completed | 272 ms |
| 20 days ago | Handshake completed | 114 ms |
| 22 days ago | Handshake completed | 94 ms |
| 24 days ago | Handshake completed | 225 ms |
| 26 days ago | Handshake completed | 90 ms |
| 28 days ago | Handshake completed | 98 ms |
| 29 days ago | Handshake completed | 89 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.
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 Payload Validator and makes no claim about it beyond what these checks measured.