RevClamp MCP Server
com-revclamp-revclamp-mcp declares 9 capabilities across 9 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
9 of 9 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.
9 of 9 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.
9 of 9 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.
9 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
revclamp_audit_revenue_leakage | read |
declared |
revclamp_evaluate_ghost_usage | read |
declared |
revclamp_stage_stripe_dispute_ce3 | read |
declared |
revclamp_validate_eu_vat_vies | read |
declared |
revclamp_reconcile_b2b_net_terms | read |
declared |
revclamp_verify_webhook_signature | read |
declared |
revclamp_calculate_roi_and_plan_fit | read |
declared |
revclamp_simulate_webhook_replay | read |
declared |
revclamp_lint_dispute_evidence | read |
declared |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.