Relay
io-github-relayprotocol-relay-mcp declares 8 capabilities across 8 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
8 of 8 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.
8 of 8 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.
8 of 8 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.
8 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
get_supported_chains | read |
inferred |
get_supported_tokens | read |
inferred |
get_bridge_quote | read |
inferred |
get_swap_quote | read |
inferred |
estimate_fees | read |
inferred |
get_transaction_status | read |
inferred |
get_transaction_history | read |
inferred |
get_relay_app_url | read |
inferred |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.