Remote MCP · Endpoint
H/M Content Credentials Evidence Verifier MCP server
No. H/M Content Credentials Evidence Verifier answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://agents.hogarmas.net/mcp/content-credentials
The last check completed an MCP handshake.
- Registry name
- net.hogarmas/content-credentials
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 53 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Free C2PA 2.4 triage and reproducible official trust snapshot. No media, keys, or payment.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 53 ms |
| 12 hours ago | Handshake completed | 372 ms |
| 1 day ago | Handshake completed | 371 ms |
| 2 days ago | Handshake completed | 404 ms |
| 4 days ago | Handshake completed | 344 ms |
| 4 days ago | Handshake completed | 283 ms |
| 5 days ago | Handshake completed | 107 ms |
| 6 days ago | Handshake completed | 408 ms |
| 8 days ago | Handshake completed | 507 ms |
| 11 days ago | Handshake completed | 545 ms |
| 13 days ago | Handshake completed | 298 ms |
| 16 days ago | Handshake completed | 314 ms |
| 18 days ago | Handshake completed | 321 ms |
| 20 days ago | Handshake completed | 312 ms |
| 22 days ago | Handshake completed | 408 ms |
| 24 days ago | Handshake completed | 401 ms |
| 26 days ago | Handshake completed | 298 ms |
| 28 days ago | Handshake completed | 326 ms |
| 29 days ago | Handshake completed | 617 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 H/M Content Credentials Evidence Verifier and makes no claim about it beyond what these checks measured.