Remote MCP · Endpoint

Machine Relations Index MCP server

No. Machine Relations Index answered an MCP handshake 46 minutes ago.

UpLast checked 46 minutes ago

Server URL

https://machinerelations.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.machinerelations/mri
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
142 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Machine Relations Index (MRI), created by Jaxon Parrott: the sources AI engines cite, by category.
Listing
From the official MCP registry (active).
Recent checks of Machine Relations Index
CheckedResultHandshake
46 minutes agoHandshake completed142 ms
3 days agoHandshake completed125 ms
13 days agoHandshake completed216 ms
13 days agoHandshake completed615 ms
15 days agoHandshake completed147 ms
16 days agoHandshake completed117 ms
17 days agoHandshake completed140 ms
18 days agoHandshake completed151 ms
18 days agoHandshake completed150 ms
20 days agoHandshake completed213 ms
22 days agoHandshake completed204 ms
25 days agoHandshake completed133 ms
27 days agoHandshake completed147 ms
30 days agoHandshake completed219 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 24 responding of 24.

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 Machine Relations Index and makes no claim about it beyond what these checks measured.