Skip to content

RFix MCP server

ai.rfix/mcprfix.aistreamable-httpv0.1.0Scanned

Create RF signal projects from prompts, inspect graphs, and export IQ data.

6 tools: 2 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 2 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the RFix MCP server can do

The RFix MCP server is published by rfix.ai, a domain the MCP Registry verified. It has 6 tools. It can create or change data (2 tools: rfix_plan_scenario and rfix_export_rfix_project), but cannot delete data. 4 tools only read.

1 tool brings in text other people can write (rfix_export_rfix_project).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 11, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 2Claude Code: ask
  • rfix_export_rfix_projectConvert RFIX JSON input into an importable `.rfix.gz` project file.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "convert": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • rfix_plan_scenarioALWAYS call this first for any RF scenario request.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • rfix_get_block_detailsReturn full parameter schemas and add-node templates for a small selected set of RFIX nodeTypes.No findings

    Why it is in this group

    • The name "rfix_get_block_details" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • rfix_list_blocksSearch the shipped RFIX block catalog by keyword.No findings

    Why it is in this group

    • The name "rfix_list_blocks" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • rfix_list_capabilitiesList high-level RFIX capability families for planning without flooding context.No findings

    Why it is in this group

    • The name "rfix_list_capabilities" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • rfix_search_block_catalogSearch concrete RFIX node types by natural-language keywords without returning full parameter schemas.No findings

    Why it is in this group

    • The name "rfix_search_block_catalog" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:27 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.rfix.ai/mcp: tools/list returned 6 tools to an anonymous client, including rfix_plan_scenario (write), rfix_export_rfix_project (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http rfix https://mcp.rfix.ai/mcp
claude mcp add --transport http rfix https://mcp.rfix.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__rfix__rfix_list_blocks",
      "mcp__rfix__rfix_list_capabilities",
      "mcp__rfix__rfix_search_block_catalog",
      "mcp__rfix__rfix_get_block_details"
    ],
    "ask": [
      "mcp__rfix__rfix_plan_scenario",
      "mcp__rfix__rfix_export_rfix_project"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as rfix. Review it before you use it.

Capability tags behind 1 rule
  • mcp__rfix__rfix_export_rfix_project untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.rfix/mcp/verify?hash=10921e770153318e06f19845e2e6da8cd5c9495e34f39622bec41a2097430e02" | jq -e '.changed == false'

Pinned hash 10921e770153, from Nov 11, 2026, 21:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.rfix/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.rfix/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.rfix/mcp.svg)](https://radar.anlyon.com/servers/ai.rfix/mcp)

Source: MCP Registry. Synced Oct 21, 2026, 17:43 UTC.

RFix MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the RFix MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the RFix MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the RFix MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the RFix MCP server have?

6 tools: 2 write, 4 read. rfix_plan_scenario, rfix_export_rfix_project, rfix_list_blocks, rfix_list_capabilities, rfix_search_block_catalog and rfix_get_block_details.

Does the RFix MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the RFix MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the RFix MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.