Remote MCP · Endpoint
R3PLICA AI Connector MCP server
No — it is up, but it requires credentials. R3PLICA AI Connector answered 1 hour ago with an authentication challenge rather than a session.
Auth requiredLast checked 1 hour ago
Server URL
https://mcp.r3plica.space/mcp
The endpoint is answering and asked us for credentials. That is a working server, not an outage.
- Registry name
- space.r3plica/catalog
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 16 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Catalog of certified digital replicas from premium design brands, for any MCP-compatible AI agent.
- Repository
- https://github.com/R3PLICAsrl/r3-cli
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Credentials required | — |
| 12 hours ago | Credentials required | — |
| 1 day ago | Credentials required | — |
| 2 days ago | Credentials required | — |
| 4 days ago | Credentials required | — |
| 4 days ago | Credentials required | — |
| 5 days ago | Credentials required | — |
| 7 days ago | Credentials required | — |
| 9 days ago | Credentials required | — |
| 11 days ago | Credentials required | — |
| 14 days ago | Handshake completed | 431 ms |
| 16 days ago | Handshake completed | 423 ms |
| 18 days ago | Handshake completed | 348 ms |
| 20 days ago | Handshake completed | 485 ms |
| 22 days ago | Handshake completed | 473 ms |
| 24 days ago | Handshake completed | 396 ms |
| 26 days ago | Handshake completed | 460 ms |
| 28 days ago | Handshake completed | 388 ms |
| 29 days ago | Handshake completed | 413 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 R3PLICA AI Connector and makes no claim about it beyond what these checks measured.