Remote MCP · Endpoint

fixRAgent maintenance triage MCP server

No. fixRAgent maintenance triage answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://fixragent.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.Russ4102/fixragent
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
172 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Assess a property maintenance photo: what it is, how urgent, which trade to call.
Listing
From the official MCP registry (active).
Recent checks of fixRAgent maintenance triage
CheckedResultHandshake
1 hour agoHandshake completed172 ms
2 days agoHandshake completed85 ms
4 days agoHandshake completed67 ms
6 days agoHandshake completed62 ms
8 days agoHandshake completed62 ms
10 days agoHandshake completed70 ms
11 days agoHandshake completed109 ms
13 days agoHandshake completed61 ms
14 days agoHandshake completed65 ms
15 days agoHandshake completed116 ms
18 days agoHandshake completed67 ms
19 days agoHandshake completed66 ms
21 days agoHandshake completed70 ms
22 days agoHandshake completed82 ms
23 days agoHandshake completed94 ms

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

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 fixRAgent maintenance triage and makes no claim about it beyond what these checks measured.