RevClamp MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REVCLAMP_API_KEY | No | Optional RevClamp workspace API key (rg_live_...). If omitted, the server runs in Stateless Sandbox Mode with zero database writes. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| revclamp_audit_revenue_leakageC | Runs a deterministic 90-day B2B revenue leakage and Visa CE 3.0 readiness audit across caller-supplied Stripe subscriptions (2025-03-31.basil item-level periods), usage events, and disputes. |
| revclamp_evaluate_ghost_usageB | Evaluates whether a metered API/SaaS usage event belongs to an entitled customer or represents post-cancellation / post-grace ghost usage under Stripe 2025-03-31.basil. |
| revclamp_stage_stripe_dispute_ce3C | Evaluates Visa Compelling Evidence 3.0 (CE 3.0) 120d-365d historical footprint overlap (IP / device_id) and builds a non-destructive access_activity_log draft (<= 18,000 UTF-16 code units, submit: false). |
| revclamp_validate_eu_vat_viesB | Normalizes 27 EU member states + Northern Ireland (XI) B2B VAT IDs (auto-converting Greece GR -> EL) and checks cross-border reverse-charge format eligibility locally (or simulates VIES states when demo: true). |
| revclamp_reconcile_b2b_net_termsB | Reconciles Shopify Plus B2B Net-15/30/60 wholesale invoices, upfront deposits, credit notes, and rounding tolerances using integer EUR-cent double-entry accounting. |
| revclamp_verify_webhook_signatureB | Generates and verifies raw-UTF8 HMAC-SHA256 webhook signatures for Stripe (Stripe-Signature t=,v1=), Shopify (X-Shopify-Hmac-Sha256 base64), and RevClamp (X-RevClamp-Signature) with 300s timestamp replay protection. |
| revclamp_calculate_roi_and_plan_fitB | Calculates monthly and annual B2B margin savings in integer USD cents comparing 0% take-rate flat pricing against 25%-30% chargeback contingency agencies and recommends the optimal tier. |
| revclamp_simulate_webhook_replayC | Simulates out-of-order and duplicate subscription lifecycle webhooks against a 72-hour deduplication Set and monotonic createdSec watermark vs. a naive arrival-order handler. |
| revclamp_lint_dispute_evidenceB | Lints Stripe dispute evidence[access_activity_log] payloads against the 18,000 UTF-16 code unit ceiling, non-destructive RevClamp CE 3.0 block markers, merchant note preservation, and Visa CE 3.0 two-identifier overlap. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| audit_stripe_and_vat_compliance | Guided workflow for auditing Stripe 2025-03-31.basil ghost usage, Visa CE 3.0 dispute evidence, and EU/XI B2B VAT IDs. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| RevClamp Open-Core vs Hosted Cloud Capabilities | Reference summary of the 9 local deterministic MCP tools vs. hosted REVCLAMP_API_KEY capabilities (90-day SQLite WAL ledger, 24/7 Stripe webhook outbox, and live EU VIES consultation IDs). |
TDQS
Scored across 9 tools
Most tools target clearly distinct operations (VAT validation, ROI calculation, signature verification, reconciliation). The main overlap is between revclamp_lint_dispute_evidence and revclamp_stage_stripe_dispute_ce3, which both operate on access_activity_log payloads under the same 18,000 UTF-16 code unit and CE 3.0 constraints, so an agent could occasionally misselect between linting vs. staging.
All tool names use a consistent revclamp_verb_noun pattern with predictable verbs (simulate, validate, audit, calculate, evaluate, lint, reconcile, stage, verify). This consistency makes the surface highly predictable.
Nine tools is well within the appropriate range and each tool maps to a distinct billing/revenue-audit concern. No tools appear redundant or padding the surface.
The surface covers a broad lifecycle: webhook simulation and signature verification, VAT validation, leakage auditing, ghost-usage evaluation, dispute linting/staging, and net-terms reconciliation. Minor gaps exist, such as actually submitting a dispute (only a submit: false draft is staged) and no explicit tool for creating or correcting invoices.