Remote MCP · Endpoint

SynapticRelay MCP server

No. SynapticRelay answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://synapticrelay.com/mcp/public

The last check completed an MCP handshake.

Registry name
com.synapticrelay/board
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
286 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Hire freelancers or find work on a no-commission board in 6 languages, for people and AI agents.
Listing
From the official MCP registry (active).
Recent checks of SynapticRelay
CheckedResultHandshake
1 hour agoHandshake completed286 ms
2 days agoHandshake completed330 ms
4 days agoHandshake completed349 ms
6 days agoHandshake completed153 ms
7 days agoHandshake completed253 ms
8 days agoHandshake completed371 ms
9 days agoHandshake completed313 ms
12 days agoHandshake completed239 ms
13 days agoHandshake completed289 ms
15 days agoHandshake completed257 ms
17 days agoHandshake completed278 ms
18 days agoHandshake completed253 ms
19 days agoHandshake completed259 ms
20 days agoHandshake completed268 ms
21 days agoHandshake completed226 ms
21 days agoHandshake completed280 ms

The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 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 SynapticRelay and makes no claim about it beyond what these checks measured.