io.github.revclamp/revclamp-mcp

None of its 9 tools are described as changing anything. For 9 the reading was uncertain, so no mark is shown.

• revclamp_audit_revenue_leakage

  “Run a deterministic 90-day B2B revenue leakage and chargeback readiness audit across Stripe subscriptions, AI/API usage telemetry events, and open disputes.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  6 inputs

  • dunningGracePeriodDaysinteger“Custom dunning grace window in integer days (valid range: 0 to 14, default: 3) allowed after latest_invoice_failed_at before flagging past_due subscriptions as…”
  • costPerEventCentsinteger“Estimated marginal compute or API cost per leaked usage event in integer USD cents (valid range: 1 to 100000, default: 142 i.e.”
  • customersarray“Optional array of up to 50 Stripe customer snapshots (each with id like 'cus_123', optional email, subscriptions array or list object, and subscriptionsHasMore…”
  • usageEventsarray“Optional array of up to 200 product/AI API usage telemetry events (each with stripe_customer_id or email, event_name, and occurredAtSec Unix timestamp in secon…”
  • disputesarray“Optional array of up to 50 Stripe dispute objects (each with id like 'du_123', customer, amount in cents, reason such as 'fraudulent', and status such as 'need…”
  • demoboolean“Optional simulation flag (boolean) for deterministic sample audit preview.”
• revclamp_evaluate_ghost_usage

  “Evaluate whether a specific customer's AI or API usage event constitutes unpaid ghost usage across multi-subscription Stripe 2025-03-31.basil state, enforcing fail-closed pagination (has_more must be…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  8 inputs, 1 required

  • customerIdstring“Stripe customer identifier to evaluate (format example: 'cus_9s6XKzkNRiz8i3', max 64 chars).”
  • subscriptionsrequired“Required Stripe customer subscriptions payload: either a Stripe list object ({ data: [...], has_more: false }) or a raw array of up to 50 subscription objects …”
  • usageEventobject“Optional metered usage event object containing customer_id (or stripe_customer_id), event_name, and occurred_at (or occurred_at_sec).”
  • subscriptionsHasMoreboolean“Pagination completeness flag (boolean).”
  • dunningGracePeriodDaysinteger“Dunning grace window in integer days (valid range: 0 to 14, default: 3) after latest_invoice_failed_at during which past_due subscriptions remain entitled.”
  • usageTimestampSecinteger“Optional Unix epoch timestamp in integer seconds (e.g.”
  • occurredAtSecinteger“Optional alias for usageTimestampSec: Unix epoch timestamp in integer seconds (e.g.”
  • demoboolean“Optional simulation flag (boolean) for deterministic ghost-usage preview.”
• revclamp_stage_stripe_dispute_ce3

  “Evaluate Visa Compelling Evidence 3.0 (CE 3.0) qualification across 120-to-365-day historical charges (requiring at least 2 settled, non-refunded, non-disputed prior transactions sharing IP address, …”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  9 inputs

  • disputeIdstring“Stripe dispute identifier being staged (format example: 'du_1QxyzEnterpriseDispute01', default: 'du_mcp_staged_01', max 64 chars).”
  • customerIdstring“Stripe customer identifier associated with the disputed charge (format example: 'cus_enterprise_88', default: 'cus_mcp_enterprise_01', max 64 chars).”
  • disputeReasonstring“Stripe dispute reason code (e.g.”
  • existingUncategorizedTextstring“Optional existing merchant evidence notes in Stripe evidence.uncategorized_text or access_activity_log (up to 18,000 chars) to preserve via append-only merge w…”
  • existingAccessActivityLogstring“Optional alias for existingUncategorizedText: existing merchant evidence notes in Stripe evidence.access_activity_log (up to 18,000 chars) to preserve via appe…”
  • disputedTransactionobject“Optional disputed charge snapshot object containing id (e.g.”
  • priorTransactionsarray“Optional array of up to 1000 historical Stripe charge objects (each with id, status: 'succeeded', disputed: false, refunded: false, occurredAtSec 120-365 days …”
  • usageEventsarray“Optional array of up to 200 customer product/API usage telemetry events (each with occurredAtSec Unix seconds, stripe_customer_id, and event_name) for append-o…”
  • demoboolean“Optional simulation flag (boolean) to stage a labeled sample dispute preview.”
• revclamp_validate_eu_vat_vies

  “Normalize EU-27 and Northern Ireland (XI) B2B VAT identifiers (including mandatory Greece ISO-3166 GR to EL prefix normalization) and evaluate cross-border 0% VAT reverse-charge eligibility, VIES con…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

  5 inputs, 1 required

  • sellerCountrystring“Two-letter EU-27 or XI member state prefix of the merchant's dispatch warehouse (e.g.”
  • buyerVatIdstringrequired“Required buyer EU or Northern Ireland VAT registration number to normalize and validate (e.g.”
  • viesModestring“VIES evaluation mode: 'FORMAT_ONLY' (deterministic EU/XI syntax validation without consultation), 'VALID' (deterministic active VAT simulation, default), 'INVA…”
  • consultationNumberstring“Optional VIES requester consultation reference number (e.g.”
  • demoboolean“Optional simulation flag (boolean) for deterministic VIES gateway preset evaluation.”
• revclamp_reconcile_b2b_net_terms

  “Reconcile B2B wholesale Net-15, Net-30, and Net-60 invoice deposits, partial payments, and credit notes using exact integer minor-unit (EUR/USD cent) arithmetic with zero IEEE-754 floating-point drif…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  12 inputs, 1 required

  • orderIdstring“B2B wholesale order or invoice identifier (e.g.”
  • totalOrderCentsinteger“Gross invoice total in positive integer minor currency units / cents (e.g.”
  • orderTotalCentsinteger“Alias for totalOrderCents: gross invoice total in positive integer minor currency units / cents (must be > 0).”
  • paidAmountCentsintegerrequired“Required cumulative amount collected from the buyer in non-negative integer cents (e.g.”
  • creditNoteCentsinteger“Optional post-invoice credit notes or return adjustments in integer cents (valid range: 0 to totalOrderCents, default: 0; singular alias for creditNotesCents).”
  • creditNotesCentsinteger“Optional post-invoice credit notes or return adjustments in integer cents (valid range: 0 to totalOrderCents, default: 0; plural alias for creditNoteCents).”
  • requiredDepositCentsinteger“Optional explicit upfront deposit threshold in integer cents (valid range: 0 to effectiveTotalCents).”
  • requiredDepositPercentinteger“Optional upfront deposit percentage required before releasing warehouse fulfillment hold (valid range: 0 to 100, default: 30 i.e.”
  • paymentTermsDaysinteger“Optional B2B net payment terms maturity window in integer days (allowed values: 15, 30, or 60 for Net-15, Net-30, or Net-60; default: 30).”
  • daysElapsedSinceInvoiceinteger“Optional elapsed integer days since invoice issuance (valid range: 0 to 3650, default: 5).”
  • toleranceCentsinteger“Optional rounding/FX reconciliation tolerance in integer cents (valid range: 0 to min(500, 1% of totalOrderCents), default: 0).”
  • demoboolean“Optional sandbox flag (boolean).”
• revclamp_verify_webhook_signature

  “Generate and verify canonical Stripe-Signature (t=<unix>,v1=<hex_sha256>), X-Shopify-Hmac-Sha256 (<base64_sha256>), and X-RevClamp-Signature (t=<unix>,v1=<hex_sha256>) headers over exact UTF-8 webhoo…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  7 inputs

  • providerstring“Webhook signature provider scheme to evaluate: 'stripe' (Stripe-Signature t=<sec>,v1=<hex>, default), 'shopify' (X-Shopify-Hmac-Sha256 Base64 raw UTF-8 HMAC), …”
  • secretstring“Synthetic or test webhook signing secret (default: 'whsec_test_revclamp_sandbox_secret_2026', max 256 chars).”
  • rawPayloadstring“Exact unparsed UTF-8 webhook request body string (up to 16,384 chars) used to compute the canonical SHA-256 HMAC digest.”
  • timestampSecinteger“Optional Unix epoch timestamp in integer seconds (valid range: 1 to 9999999999; defaults to current server Unix timestamp) used when generating or verifying ti…”
  • signatureHeaderstring“Optional supplied HTTP signature header value to verify via crypto.timingSafeEqual (e.g.”
  • toleranceSecinteger“Optional replay window tolerance in integer seconds (valid range: 1 to 3600, default: 300).”
  • demoboolean“Optional sandbox flag; uses synthetic defaults when provider, secret, or rawPayload are omitted.”
• revclamp_calculate_roi_and_plan_fit

  “Deterministically calculate monthly and annual B2B margin savings using exact integer USD cents when replacing a 25%-30% contingency chargeback agency with RevClamp flat-rate 0% commission plans ($19…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  4 inputs

  • monthlyWonDisputeUsdnumber“Monthly won Stripe chargeback volume in USD (valid range: 0 to 10000000, default: 10000) subject to legacy agency take-rate fees.”
  • monthlyGhostBleedUsdnumber“Monthly unpaid AI/API or SaaS usage bleed stopped by RevClamp basil entitlement guards in USD (valid range: 0 to 10000000, default: 600).”
  • contingencyTakeRatePercentnumber“Competitor chargeback agency contingency commission percentage (valid range: 1 to 50, default: 25 for 25% take-rate tools).”
  • monthlyUsageEventsinteger“Monthly verified usage events across your workspace (integer 0 to 50000000, default: 250000) used to recommend Starter (<=100k), Growth (<=1M), or Scale (<=5M).”
• revclamp_simulate_webhook_replay

  “Deterministically evaluate an ordered or out-of-order sequence of 1-10 Stripe/Shopify/RevClamp subscription lifecycle webhooks against a 72-hour idempotency deduplication Set (eventId), a configurabl…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  5 inputs

  • scenarioPresetstring“Scenario preset to evaluate when custom events are omitted (default: 'out_of_order_stale_update_after_cancel').”
  • eventsarray“Optional custom array of 1 to 10 webhook events ({ eventId, eventType, createdSec, subscriptionStatus, tier, currentPeriodEndSec }) in arrival order.”
  • nowSecinteger“Reference evaluation timestamp in Unix seconds used to check the 72-hour idempotency window.”
  • idempotencyWindowSecinteger“Deduplication and replay-acceptance window in seconds (valid range: 60 to 2592000, default: 259200 for 72 hours).”
  • demoboolean“Optional sandbox flag to run the preset replay simulation.”
• revclamp_lint_dispute_evidence

  “Deterministically lint a Stripe dispute evidence[access_activity_log] payload against Stripe's 18,000 UTF-16 code unit (String.prototype.length) ceiling, UTF-8 byte length, non-destructive --- BEGIN …”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  6 inputs

  • presetstring“Scenario preset to evaluate when custom evidenceLogText is omitted (default: 'valid_ce3_non_destructive').”
  • existingMerchantNotesstring“Existing human AE/support notes inside evidence[access_activity_log] that must be preserved.”
  • evidenceLogTextstring“Merged or candidate Stripe dispute evidence[access_activity_log] payload evaluated against the 18,000 UTF-16 code unit ceiling and non-destructive delimiter ma…”
  • priorMatchedCountinteger“Number of prior undisputed Stripe charges (120d-365d old) with matching customer_id and IP/device fingerprint (Visa CE 3.0 requires >= 2).”
  • hasIpMatchboolean“Whether the disputed charge IPv4/IPv6 address matches the historical undisputed charges.”
  • hasDeviceMatchboolean“Whether the disputed charge device_id fingerprint matches the historical undisputed charges.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-26.

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.