Remote MCP · Endpoint

RFix MCP server

No. RFix answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.rfix.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.rfix/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
76 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Create RF signal projects from prompts, inspect graphs, and export IQ data.
Listing
From the official MCP registry (active).
Recent checks of RFix
CheckedResultHandshake
2 hours agoHandshake completed76 ms
1 day agoHandshake completed78 ms
3 days agoHandshake completed85 ms
3 days agoHandshake completed95 ms
4 days agoHandshake completed209 ms
5 days agoHandshake completed78 ms
7 days agoHandshake completed89 ms
10 days agoHandshake completed79 ms
12 days agoHandshake completed68 ms
15 days agoHandshake completed67 ms
17 days agoHandshake completed81 ms
19 days agoHandshake completed121 ms
21 days agoHandshake completed110 ms
23 days agoHandshake completed75 ms
25 days agoHandshake completed72 ms
26 days agoHandshake completed91 ms
28 days agoHandshake completed94 ms
29 days agoHandshake completed84 ms

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

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