Remote MCP · Endpoint
Agent Reputation Registry MCP server
No. Agent Reputation Registry answered an MCP handshake 5 hours ago.
UpLast checked 5 hours ago
Server URL
https://rep.memoryapi.org/mcp
The last check completed an MCP handshake.
- Registry name
- org.memoryapi/rep
- Transport
- Streamable HTTP
- Protocol negotiated
- 2024-11-05
- Handshake latency
- 377 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 23.5% from 17 checks
- Described by its publisher as
- Agent reputation registry: check, register, and endorse AI agents
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 5 hours ago | Handshake completed | 377 ms |
| 2 days ago | Handshake completed | 125 ms |
| 4 days ago | Handshake completed | 128 ms |
| 5 days ago | Handshake completed | 140 ms |
| 7 days ago | Failed - the hostname does not resolve | — |
| 8 days ago | Failed - the hostname does not resolve | — |
| 9 days ago | Failed - the hostname does not resolve | — |
| 12 days ago | Failed - the hostname does not resolve | — |
| 13 days ago | Failed - the hostname does not resolve | — |
| 15 days ago | Failed - the hostname does not resolve | — |
| 16 days ago | Failed - the hostname does not resolve | — |
| 17 days ago | Failed - the hostname does not resolve | — |
| 18 days ago | Failed - the hostname does not resolve | — |
| 19 days ago | Failed - the hostname does not resolve | — |
| 20 days ago | Failed - the hostname does not resolve | — |
| 21 days ago | Failed - the hostname does not resolve | — |
| 22 days ago | Failed - the hostname does not resolve | — |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 4 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 Agent Reputation Registry and makes no claim about it beyond what these checks measured.