RFix
REMOTE · MCP.RFIX.AI · SCANNED SEP 24
Create RF signal projects from prompts, inspect graphs, and export IQ data.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 769 tokens (~109/item across 7 items; 3 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
How do I install the RFix MCP server?
RFix is a hosted endpoint at https://mcp.rfix.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.rfix.ai
claude mcp add --transport http ai-rfix-mcp 'https://mcp.rfix.ai/mcp'
{
"mcpServers": {
"ai-rfix-mcp": {
"url": "https://mcp.rfix.ai/mcp"
}
}
} {
"servers": {
"ai-rfix-mcp": {
"type": "http",
"url": "https://mcp.rfix.ai/mcp"
}
}
} [mcp_servers.ai-rfix-mcp] url = "https://mcp.rfix.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-rfix-mcp": {
"type": "remote",
"url": "https://mcp.rfix.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-rfix-mcp --url 'https://mcp.rfix.ai/mcp' --transport streamable-http
mcp_servers:
ai-rfix-mcp:
url: "https://mcp.rfix.ai/mcp" {
"McpServers": {
"ai-rfix-mcp": {
"Transport": "http",
"Url": "https://mcp.rfix.ai/mcp"
}
}
} assistant mcp add ai-rfix-mcp -t streamable-http -u 'https://mcp.rfix.ai/mcp'
{
"mcpServers": {
"ai-rfix-mcp": {
"type": "http",
"url": "https://mcp.rfix.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 78
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://mcp.rfix.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.rfix.ai | CN=WR3,O=Google Trust Services,C=US | 2 Aug 2026 | 31 Oct 2026 | RSA 2048 | SHA256-RSA | c89881414a24442c10d61e7b90cc959a |
| SANs: mcp.rfix.ai | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.rfix.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| rfix.ai. | present | 2371 | 13 | Verified |
| mcp.rfix.ai. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.rfix.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.rfix.ai/mcp | HTTPS enforced | 302 | https://mcp.rfix.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
rfix_export_rfix_project ~107
Convert RFIX JSON input into an importable `.rfix.gz` project file. `payload` may be an RFIX backend payload, GCF prompt graph output, exported graph data, or editor/.rfix-style project JSON. Project-shaped input is preserved where possible; backend payload input is reverse-transformed into a legacy flat project. In server-side mode this also publishes launch URLs for desktop and web.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact_name | – | – | – |
| payload | object | yes | – |
No output schema declared.
No examples provided.
rfix_list_blocks ~86
Search the shipped RFIX block catalog by keyword. Use this when you need to find specific block types not already returned by rfix_plan_scenario. Queries like radar, ship, aircraft, communication, 3d, doppler, dmr, or wifi return relevant blocks with parameter schemas. Includes parameter schemas inline.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | – | – | – |
No output schema declared.
No examples provided.
rfix_plan_scenario ~95
ALWAYS call this first for any RF scenario request. Returns block schemas, composition rules, constraints, and a reference example payload. YOU must compose your own graph/project using this guidance, then call rfix_export_rfix_project. Do NOT search the filesystem for blocks or examples — this tool returns everything needed.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| prefer_simple | boolean | – | – |
| reasoning_mode | string | – | – |
No output schema declared.
No examples provided.
What is the RFix MCP server?
RFix is an MCP server listed in the public MCP registry as ai.rfix/mcp. Create RF signal projects from prompts, inspect graphs, and export IQ data. This page covers its hosted endpoint (https://mcp.rfix.ai/mcp).
Is the RFix MCP server safe to use?
RFix scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the RFix MCP server expose?
RFix exposes 3 tools: rfix_plan_scenario, rfix_list_blocks, rfix_export_rfix_project. Their descriptions and schemas cost roughly 288 tokens of context every time the server is loaded.
Does the RFix MCP server require authentication?
No. We connected to RFix without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RFix MCP server still maintained?
RFix is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.