Create RF signal projects from prompts, inspect graphs, and export IQ data.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://mcp.rfix.ai/mcp3 tools · 978msrfix_plan_scenarioALWAYS 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.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.
No input schema was published for this tool.
rfix_list_blocksSearch 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.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.
No input schema was published for this tool.
rfix_export_rfix_projectConvert 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.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.
No input schema was published for this tool.
3 of 3 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Create RF signal projects from prompts, inspect graphs, and export IQ data.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.