mcp server
RFix
Create RF signal projects from prompts, inspect graphs, and export IQ data.
Description as published by the maintainer. Source
- version 0.1.0
- active
active — Registry entry last updated 2026-06-04.
What this server can do
3 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
rfix_export_rfix_project(payload, artifact_name)- 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. Required: payload.
rfix_list_blocks(limit, query)- 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.
rfix_plan_scenario(description, prefer_simple, reasoning_mode)- 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. Required: description.
Last successful function declaration observed on . Source: https://mcp.rfix.ai/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.rfix.ai/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-04 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-04 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 3 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.rfix.ai | |
| mcp endpoint status | ok | The server listed 3 functions when asked. | as of probe | mcp.rfix.ai |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json