Remote MCP · Endpoint

Relin MCP server

No. Relin answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://relin.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.earonesty/relin
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
852 ms
Tools exposed
53 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Send and receive webhooks, manage customer endpoints, and inspect and retry deliveries.
Listing
From the official MCP registry (active).
Recent checks of Relin
CheckedResultHandshake
2 hours agoHandshake completed852 ms
2 days agoHandshake completed525 ms
4 days agoHandshake completed304 ms
5 days agoHandshake completed368 ms
7 days agoHandshake completed383 ms
8 days agoHandshake completed432 ms
9 days agoHandshake completed386 ms
12 days agoHandshake completed308 ms
13 days agoHandshake completed539 ms
15 days agoHandshake completed410 ms
17 days agoHandshake completed403 ms
18 days agoHandshake completed607 ms
19 days agoHandshake completed303 ms
20 days agoHandshake completed278 ms
20 days agoHandshake completed246 ms
21 days agoHandshake completed277 ms
23 days agoHandshake completed296 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 Relin and makes no claim about it beyond what these checks measured.