ai.rfix/mcp · v0.1.0 · marketing-and-seo
RFix is healthy: it completed an MCP handshake in 1221 ms and exposes 6 tools. It scores 59/100.
Create RF signal projects from prompts, inspect graphs, and export IQ data.
Endpoint: https://mcp.rfix.ai/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| health | 21.1 / 25 |
| authEase | 15 / 15 |
| toolQuality | 15 / 15 |
| maintenance | 3 / 15 |
| adoption | 0 / 10 |
| usage | 0 / 10 |
| security | 5 / 10 |
Scoring v0.3, computed 2026-10-14T20:21:24.341Z.
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-14T12:15:38.519Z | Healthy | 1221 |
rfix_plan_scenario | 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 |
rfix_list_blocks | 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 inl |
rfix_list_capabilities | List high-level RFIX capability families for planning without flooding context. Use this before block search when the request is broad, then call rfix_search_block_catalog for likely concrete node types. |
rfix_search_block_catalog | Search concrete RFIX node types by natural-language keywords without returning full parameter schemas. Use this before constructing add_node actions, then call rfix_get_block_details for the selected nodeTypes. |
rfix_get_block_details | Return full parameter schemas and add-node templates for a small selected set of RFIX nodeTypes. Call this only after rfix_search_block_catalog has narrowed the relevant blocks. |
rfix_export_rfix_project | 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 |