Remote MCP · Endpoint
com.verisgov.api/data-access MCP server
No. com.verisgov.api/data-access answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.verisgov.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.verisgov.api/data-access
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 554 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Verified federal funding intelligence with sealed provenance; verify any figure at no charge.
- Website
- https://www.verisgov.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 554 ms |
| 2 days ago | Handshake completed | 564 ms |
| 4 days ago | Handshake completed | 530 ms |
| 5 days ago | Handshake completed | 621 ms |
| 7 days ago | Handshake completed | 824 ms |
| 8 days ago | Handshake completed | 817 ms |
| 9 days ago | Handshake completed | 532 ms |
| 12 days ago | Handshake completed | 452 ms |
| 13 days ago | Handshake completed | 564 ms |
| 15 days ago | Handshake completed | 398 ms |
| 16 days ago | Handshake completed | 941 ms |
| 18 days ago | Handshake completed | 449 ms |
| 19 days ago | Handshake completed | 442 ms |
| 20 days ago | Handshake completed | 415 ms |
| 20 days ago | Handshake completed | 380 ms |
| 21 days ago | Handshake completed | 396 ms |
| 22 days ago | Handshake completed | 608 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 com.verisgov.api/data-access and makes no claim about it beyond what these checks measured.