RFix
ai-rfix-mcp declares 6 capabilities across 6 tools, with 1 critical issue. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.
Issues
6 of 6 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
6 of 6 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
6 of 6 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
1 tool can modify data and declares no limit.
5 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
rfix_plan_scenario | read |
declared |
rfix_list_blocks | read |
declared |
rfix_list_capabilities | read |
declared |
rfix_search_block_catalog | read |
declared |
rfix_get_block_details | read |
declared |
rfix_export_rfix_project | write |
assumed |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-05 | 10 | tools/list on https://mcp.rfix.ai/mcp, published in the official MCP registry as ai.rfix/mcp 0.1.0 |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.