Remote MCP · Endpoint
attest — verification for AI agent artifacts MCP server
No. attest — verification for AI agent artifacts answered an MCP handshake 53 minutes ago.
UpLast checked 53 minutes ago
Server URL
https://attest.rta.lat/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.mrpkk/attest
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 3.31 s
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 92.9% from 14 checks
- Described by its publisher as
- Verify artifacts produced by AI agents: schema, emptiness, provenance, authority.
- Repository
- https://github.com/mrpkk/attest
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 53 minutes ago | Handshake completed | 3.31 s |
| 3 days ago | Handshake completed | 494 ms |
| 12 days ago | Handshake completed | 468 ms |
| 13 days ago | Handshake completed | 568 ms |
| 15 days ago | Failed - the server returned an HTTP error | — |
| 15 days ago | Handshake completed | 703 ms |
| 17 days ago | Handshake completed | 1.77 s |
| 18 days ago | Handshake completed | 810 ms |
| 18 days ago | Handshake completed | 533 ms |
| 20 days ago | Handshake completed | 935 ms |
| 22 days ago | Handshake completed | 665 ms |
| 25 days ago | Handshake completed | 532 ms |
| 27 days ago | Handshake completed | 1.79 s |
| 29 days ago | Handshake completed | 595 ms |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 16.
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 attest — verification for AI agent artifacts and makes no claim about it beyond what these checks measured.