402MCP.org — HTTP 402 & Agent Payment Registry
org-402mcp-registry declares 7 capabilities across 7 tools, with 3 critical issues.
Issues
7 of 7 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.
1 tool is classified as irreversible and declares no limit.
1 tool is classified as moving money and declares no dollar limit. A cap on the number of payments does not bound their amount.
7 of 7 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.
7 of 7 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.
6 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
decode_402_challenge | read |
declared |
recommend_payment_rail | pay |
inferred |
search_402_solutions | read |
declared |
get_solution | read |
declared |
get_scheme_reference | read |
declared |
probe_402_support | read |
declared |
get_best_payment_solution | read |
declared |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.