# RevClamp MCP Server (remote · api.revclamp.com) Zero-take-rate Stripe 2025-03-31.basil, Visa CE 3.0 & EU/UK VIES VAT guardrails MCP server. - Trust score: 74/100 (medium) - Change this week: +4 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - remote · `api.revclamp.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/revclamp-revclamp-mcp/api-mcp.md), [page](https://verifymcp.io/servers/revclamp-revclamp-mcp/api-mcp) ## Channel facts - Endpoint: `https://api.revclamp.com/api/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `1.20.7` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Endpoint Security**: 80/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. - HTTPS is enforced; there's no plaintext access path. - The HSTS (Strict-Transport-Security) header is present. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 56/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 4540 tokens (~504/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 37/100 - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 60/100 - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. ## Install ### How do I install the RevClamp MCP Server server? RevClamp MCP Server is a hosted endpoint at https://api.revclamp.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add --transport http revclamp-revclamp-mcp 'https://api.revclamp.com/api/mcp' ``` ### Cursor ```json { "mcpServers": { "revclamp-revclamp-mcp": { "url": "https://api.revclamp.com/api/mcp" } } } ``` ### VS Code ```json { "servers": { "revclamp-revclamp-mcp": { "type": "http", "url": "https://api.revclamp.com/api/mcp" } } } ``` ### Codex ```toml [mcp_servers.revclamp-revclamp-mcp] url = "https://api.revclamp.com/api/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "revclamp-revclamp-mcp": { "type": "remote", "url": "https://api.revclamp.com/api/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add revclamp-revclamp-mcp --url 'https://api.revclamp.com/api/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: revclamp-revclamp-mcp: url: "https://api.revclamp.com/api/mcp" ``` ### Netclaw ```json { "McpServers": { "revclamp-revclamp-mcp": { "Transport": "http", "Url": "https://api.revclamp.com/api/mcp" } } } ``` ### Vellum ```bash assistant mcp add revclamp-revclamp-mcp -t streamable-http -u 'https://api.revclamp.com/api/mcp' ``` ### Other ```json { "mcpServers": { "revclamp-revclamp-mcp": { "type": "http", "url": "https://api.revclamp.com/api/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-05 (score 74, +1) - [functional] Server version: 1.20.19 → 1.20.20 ### 2026-11-03 (score 73, +1) No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-11-02 (score 72, 0) - [functional] Server version: 1.20.17 → 1.20.19 ### 2026-11-01 (score 72, +1) - [functional] Server version: 1.20.13 → 1.20.17 ### 2026-10-31 (score 71, 0) - [functional] Server version: 1.20.11 → 1.20.13 - [cosmetic] “revclamp_validate_eu_vat_vies” added an optional parameter “supplyType” - [cosmetic] “revclamp_validate_eu_vat_vies” reworded the description of “viesMode” ### 2026-10-30 (score 71, +1) - [functional] Server version: 1.20.10 → 1.20.11 ### 2026-10-29 (score 70, 0) - [security] Tool “revclamp_lint_dispute_evidence” rewrote its description, which is the text the model reads - [functional] Server version: 1.20.8 → 1.20.10 - [cosmetic] “revclamp_lint_dispute_evidence” added an optional parameter “accessActivityLog” - [cosmetic] “revclamp_lint_dispute_evidence” added an optional parameter “demo” - [cosmetic] “revclamp_lint_dispute_evidence” added an optional parameter “disputedTransaction” - [cosmetic] “revclamp_lint_dispute_evidence” added an optional parameter “priorTransactions” - [cosmetic] “revclamp_verify_webhook_signature” added an optional parameter “secrets” - [cosmetic] “revclamp_lint_dispute_evidence” reworded the description of “preset” - [cosmetic] “revclamp_verify_webhook_signature” reworded the description of “secret” ### 2026-10-28 (score 70, 0) - [functional] Server version: 1.20.7 → 1.20.8 ## MCP tools (9) ### `revclamp_audit_revenue_leakage` (~435 tokens) Audit B2B Revenue Leakage & Dispute Readiness Run a deterministic 90-day B2B revenue leakage and chargeback readiness audit across Stripe subscriptions, AI/API usage telemetry events, and open disputes. Executes as a 100% read-only, stateless diagnostic with zero external Stripe mutations. Returns structuredContent containing ok, mode, statelessEphemeralAudit, tenantId, dunningGracePeriodDays, costPerEventCents, and audit (scannedCustomers, scannedEvents, ghostLeakEventsCount, affectedCustomersCount, estimatedBleedUsd, disputesEligibleForAutoEvidence). Use this tool for portfolio-wide multi-customer audits; use revclamp_evaluate_ghost_usage for single-customer entitlement checks or revclamp_stage_stripe_dispute_ce3 to build a single dispute's Visa CE 3.0 evidence bundle. Input parameters: - `costPerEventCents` (integer): Estimated marginal compute or API cost per leaked usage event in integer USD cents (valid range: 1 to 100000, default: 142 i.e. $1.42/event). - `customers` (array): Optional array of up to 50 Stripe customer snapshots (each with id like 'cus_123', optional email, subscriptions array or list object, and subscriptionsHasMore: false). Omit to run against workspace… - `demo` (boolean): Optional simulation flag (boolean) for deterministic sample audit preview. - `disputes` (array): 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 'needs_response'). - `dunningGracePeriodDays` (integer): 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 unpaid ghost usage. - `usageEvents` (array): 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 seconds). ### `revclamp_evaluate_ghost_usage` (~481 tokens) Evaluate Single-Customer Stripe Basil 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 explicitly false) and configurable 0-14 day dunning grace windows. Executes as a stateless, read-only entitlement evaluator with zero side effects. Returns structuredContent containing ok, mode, statelessEphemeralAudit, tenantId, and evaluation (isGhostLeak, isGhostUsage, reason). Use this tool for real-time per-customer entitlement gating; use revclamp_audit_revenue_leakage for batch multi-customer portfolio audits. Input parameters: - `customerId` (string): Stripe customer identifier to evaluate (format example: 'cus_9s6XKzkNRiz8i3', max 64 chars). - `demo` (boolean): Optional simulation flag (boolean) for deterministic ghost-usage preview. - `dunningGracePeriodDays` (integer): 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. - `occurredAtSec` (integer): Optional alias for usageTimestampSec: Unix epoch timestamp in integer seconds (e.g. 1761264000) when the usage event occurred (used when usageTimestampSec is omitted). - `subscriptions` (required): Required Stripe customer subscriptions payload: either a Stripe list object ({ data: [...], has_more: false }) or a raw array of up to 50 subscription objects containing id, status ('active', 'triali… - `subscriptionsHasMore` (boolean): Pagination completeness flag (boolean). Must be explicitly set to false when passing a raw subscriptions array so RevClamp can verify no active subscription was truncated on a later page. - `usageEvent` (object): Optional metered usage event object containing customer_id (or stripe_customer_id), event_name, and occurred_at (or occurred_at_sec). - `usageTimestampSec` (integer): Optional Unix epoch timestamp in integer seconds (e.g. 1761264000) when the AI/API usage event occurred (defaults to current server Unix timestamp if omitted). ### `revclamp_stage_stripe_dispute_ce3` (~583 tokens) Stage Visa CE 3.0 Stripe Dispute Evidence Draft 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, device fingerprint, or billing email) and assemble a non-destructive Stripe dispute evidence draft with submit hardcoded to false. Executes as a pure read-only staging computation that never auto-submits to card networks. Returns structuredContent containing ok, mode, statelessEphemeralAudit, tenantId, submitForcedFalse, ce3Qualification, and drawer (including stripeUpdateParams with submit: false and merged access_activity_log). Use this tool for single-dispute CE 3.0 qualification and evidence staging; use revclamp_audit_revenue_leakage for portfolio-wide dispute readiness counts. Input parameters: - `customerId` (string): Stripe customer identifier associated with the disputed charge (format example: 'cus_enterprise_88', default: 'cus_mcp_enterprise_01', max 64 chars). - `demo` (boolean): Optional simulation flag (boolean) to stage a labeled sample dispute preview. - `disputeId` (string): Stripe dispute identifier being staged (format example: 'du_1QxyzEnterpriseDispute01', default: 'du_mcp_staged_01', max 64 chars). - `disputeReason` (string): Stripe dispute reason code (e.g. 'fraudulent', 'unrecognized', 'subscription_canceled', 'product_unacceptable', 'general'; default: 'fraudulent'; Visa CE 3.0 applies to 'fraudulent' disputes). - `disputedTransaction` (object): Optional disputed charge snapshot object containing id (e.g. 'ch_disputed_01'), occurredAtSec (Unix seconds), customer_id, email, ip_address, and device_id. - `existingAccessActivityLog` (string): Optional alias for existingUncategorizedText: existing merchant evidence notes in Stripe evidence.access_activity_log (up to 18,000 chars) to preserve via append-only merge. - `existingUncategorizedText` (string): 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 without overwriting. - `priorTransactions` (array): Optional array of up to 1000 historical Stripe charge objects (each with id, status: 'succeeded', disputed: false, refunded: false, occurredAtSec 120-365 days prior to disputedTransaction, email, ip_… - `usageEvents` (array): 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-only access_activity_log staging. ### `revclamp_validate_eu_vat_vies` (~546 tokens) Validate EU/XI B2B VAT ID & VIES Reverse-Charge State 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 consultation evidence, or MS_UNAVAILABLE circuit-breaker fulfillment hold actions. Read-only and non-destructive; supports deterministic simulation modes ('VALID', 'INVALID', 'MS_UNAVAILABLE') or real-time European Commission VIES SOAP/REST lookup ('LIVE'). Returns structuredContent containing ok, mode, statelessEphemeralAudit, simulatedViesLookup, tenantId, normalizedVat, reverseChargeEligible, and viesDecision (status, action, zeroRateAllowed, consultationId). Use this tool for EU/XI VAT tax compliance; use revclamp_reconcile_b2b_net_terms for wholesale Net-15/30/60 deposit and credit-note accounting. Input parameters: - `buyerVatId` (string, required): Required buyer EU or Northern Ireland VAT registration number to normalize and validate (e.g. 'DE123456789', 'GR123456789', 'NL123456789B01', 'XI123456789', max 40 chars). - `consultationNumber` (string): Optional VIES requester consultation reference number (e.g. 'WAPIAAAAW998877', max 64 chars) to attach to deterministic 'VALID' mode tax audit records. - `demo` (boolean): Optional simulation flag (boolean) for deterministic VIES gateway preset evaluation. - `sellerCountry` (string): Two-letter EU-27 or XI member state prefix of the merchant's dispatch warehouse (e.g. 'DE', 'NL', 'FR', 'EL', 'XI'; 'GR' is automatically normalized to 'EL'; default: 'DE'). - `supplyType` (string): Cross-border transaction supply category: 'GOODS' (Directive 2006/112/EC Art. 138(1) intra-Community supply, default; permitted for Northern Ireland XI under Windsor Framework) or 'SERVICES' (Directi… - `viesMode` (string): VIES evaluation mode: 'FORMAT_ONLY' (deterministic EU/XI syntax validation without consultation; local engine default), 'VALID' (deterministic active VAT simulation; cloud endpoint default), 'INVALID… ### `revclamp_reconcile_b2b_net_terms` (~647 tokens) Reconcile B2B Wholesale Net-15/30/60 Deposits & Credit Notes 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 drift. Executes as a pure, stateless, read-only financial reconciliation function. Returns structuredContent containing ok, mode, statelessEphemeralAudit, tenantId, and reconciliation (state, status, fulfillmentHold, releaseHoldAction, requiredDepositCents, remainingBalanceCents, creditDueCents, overpaidWarning, orderTag). Use this tool for B2B wholesale order deposit gating and Net-terms balance calculation; use revclamp_validate_eu_vat_vies for cross-border EU VAT number validation. Input parameters: - `creditNoteCents` (integer): Optional post-invoice credit notes or return adjustments in integer cents (valid range: 0 to totalOrderCents, default: 0; singular alias for creditNotesCents). - `creditNotesCents` (integer): Optional post-invoice credit notes or return adjustments in integer cents (valid range: 0 to totalOrderCents, default: 0; plural alias for creditNoteCents). - `daysElapsedSinceInvoice` (integer): Optional elapsed integer days since invoice issuance (valid range: 0 to 3650, default: 5). - `demo` (boolean): Optional sandbox flag (boolean). - `orderId` (string): B2B wholesale order or invoice identifier (e.g. 'gid://shopify/Order/908812' or 'ORD-2026-9088', default: 'ord_local_b2b_01', max 64 chars). - `orderTotalCents` (integer): Alias for totalOrderCents: gross invoice total in positive integer minor currency units / cents (must be > 0). - `paidAmountCents` (integer, required): Required cumulative amount collected from the buyer in non-negative integer cents (e.g. 75000 for 750.00 EUR; must be >= 0). - `paymentTermsDays` (integer): 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). - `requiredDepositCents` (integer): Optional explicit upfront deposit threshold in integer cents (valid range: 0 to effectiveTotalCents). Overrides requiredDepositPercent when provided. - `requiredDepositPercent` (integer): Optional upfront deposit percentage required before releasing warehouse fulfillment hold (valid range: 0 to 100, default: 30 i.e. 30% upfront deposit). - `toleranceCents` (integer): Optional rounding/FX reconciliation tolerance in integer cents (valid range: 0 to min(500, 1% of totalOrderCents), default: 0). - `totalOrderCents` (integer): Gross invoice total in positive integer minor currency units / cents (e.g. 250000 for 2,500.00 EUR; must be > 0). ### `revclamp_verify_webhook_signature` (~649 tokens) Verify Stripe, Shopify & RevClamp Webhook HMAC-SHA256 Signatures Generate and verify canonical Stripe-Signature (t=,v1=), X-Shopify-Hmac-Sha256 (), and X-RevClamp-Signature (t=,v1=) headers over exact UTF-8 webhook payload bytes using crypto.timingSafeEqual and a 300-second replay window guard. Enforces a Zero-Trust guard that blocks known live/production credential patterns (sk_live_, rk_live_, non-test whsec_..., shpss_..., shpat_..., rg_live_, rc_live_, AKIA..., and PEM private keys) with -32602 LIVE_SECRET_FORBIDDEN_IN_SANDBOX. Returns structuredContent containing ok, mode, statelessEphemeralAudit, tenantId, and verification (provider, verificationMode, headerName, generatedHeader, expectedSignature, signatureValid, verificationReason, timingSafeCompared, replayWindowApplicable, timestampSec, timestampSkewSeconds, toleranceSeconds, withinReplayWindow, payloadByteLength, payloadSha256, commonIntegrationTrap). Use this tool to debug webhook signature mismatches and replay skew. Input parameters: - `demo` (boolean): Optional sandbox flag; uses synthetic defaults when provider, secret, or rawPayload are omitted. - `provider` (string): Webhook signature provider scheme to evaluate: 'stripe' (Stripe-Signature t=,v1=, default), 'shopify' (X-Shopify-Hmac-Sha256 Base64 raw UTF-8 HMAC), or 'revclamp' (X-RevClamp-Signature t== lastAppliedCreatedSec). Compares RevClamp's monotonic FSM against a naive overwrite-on-arrival handler to detect resurrected canceled subscriptions, stale tier downgrades, and duplicate retry side-effects. Returns structuredContent containing ok, mode, statelessEphemeralAudit, tenantId, simulation, steps, finalStatus, finalTier, finalEntitlementDecision, naiveFinalStatus, and naiveHandlerBug. Input parameters: - `demo` (boolean): Optional sandbox flag to run the preset replay simulation. - `events` (array): Optional custom array of 1 to 10 webhook events ({ eventId, eventType, createdSec, subscriptionStatus, tier, currentPeriodEndSec }) in arrival order. - `idempotencyWindowSec` (integer): Deduplication and replay-acceptance window in seconds (valid range: 60 to 2592000, default: 259200 for 72 hours). - `nowSec` (integer): Reference evaluation timestamp in Unix seconds used to check the 72-hour idempotency window. - `scenarioPreset` (string): Scenario preset to evaluate when custom events are omitted (default: 'out_of_order_stale_update_after_cancel'). ### `revclamp_lint_dispute_evidence` (~559 tokens) Stripe Dispute Evidence UTF-16 & CE 3.0 Completeness Linter 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 REVCLAMP CE3 EVIDENCE --- / --- END REVCLAMP CE3 EVIDENCE --- (or [RevClamp Verified Product Usage Log] / [/RevClamp Verified Product Usage Log]) delimiter markers, existing merchant note preservation, 17,922/17,920-char fixed wrapper capacity threshold (SKIP_POST_PRESERVE_DRAFT), and Visa Compelling Evidence 3.0 (CE 3.0) prior-charge (>= 2) + IP/device overlap qualification. Returns structuredContent containing ok, mode, statelessEphemeralAudit, tenantId, lint, utf16CodeUnits, maxUtf16Ceiling, remainingUtf16Units, withinCeiling, utf8Bytes, nonDestructiveMarkersPresent, merchantNotesPreserved, merchantNotesUtf16CodeUnits, fixedWrapperUtf16CodeUnits, merchantLogAtCapacity, stagingActionWhenAtCapacity, priorMatchedCount, hasIpMatch, hasDeviceMatch, ce3RubricPassed, and overallVerdict. Input parameters: - `accessActivityLog` (string): Alias for evidenceLogText representing Stripe dispute evidence[access_activity_log] payload. - `demo` (boolean): Set true to lint a sample preset fixture when evidenceLogText / accessActivityLog is omitted. - `disputedTransaction` (object): Optional disputed Stripe charge/transaction metadata evaluated against priorTransactions for Visa CE 3.0 qualification. - `evidenceLogText` (string): Merged or candidate Stripe dispute evidence[access_activity_log] payload evaluated against the 18,000 UTF-16 code unit ceiling and non-destructive delimiter markers. - `existingMerchantNotes` (string): Existing human AE/support notes inside evidence[access_activity_log] that must be preserved. - `hasDeviceMatch` (boolean): Whether the disputed charge device_id fingerprint matches the historical undisputed charges. - `hasIpMatch` (boolean): Whether the disputed charge IPv4/IPv6 address matches the historical undisputed charges. - `preset` (string): Scenario preset to evaluate when custom evidenceLogText / accessActivityLog is omitted (default: 'valid_ce3_non_destructive'). - `priorMatchedCount` (integer): Number of prior undisputed Stripe charges (120d-365d old) with matching customer_id and IP/device fingerprint (Visa CE 3.0 requires >= 2). - `priorTransactions` (array): Optional historical undisputed Stripe charges (120d-365d prior) evaluated for Visa CE 3.0 two-identifier overlap. ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/revclamp-revclamp-mcp/api-mcp#diagnostics ## Score history - 2026-11-05: 74 - 2026-11-04: 73 - 2026-11-03: 73 - 2026-11-02: 72 - 2026-11-01: 72 - 2026-10-31: 71 - 2026-10-30: 71 - 2026-10-29: 70 - 2026-10-28: 70 - 2026-10-27: 70 - 2026-10-26: 69 - 2026-10-25: 69 ## Common questions ### What is the RevClamp MCP Server server? RevClamp MCP Server is listed in the public MCP registry as io.github.revclamp/revclamp-mcp. Zero-take-rate Stripe 2025-03-31.basil, Visa CE 3.0 & EU/UK VIES VAT guardrails MCP server. This page covers its hosted endpoint (https://api.revclamp.com/api/mcp). ### Is the RevClamp MCP Server server safe to use? RevClamp MCP Server scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the RevClamp MCP Server server expose? RevClamp MCP Server exposes 9 tools: revclamp_audit_revenue_leakage, revclamp_evaluate_ghost_usage, revclamp_stage_stripe_dispute_ce3, revclamp_validate_eu_vat_vies, revclamp_reconcile_b2b_net_terms, and 4 more. Their descriptions and schemas cost roughly 4,540 tokens of context every time the server is loaded. ### Does the RevClamp MCP Server server require authentication? No. We connected to RevClamp MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address. ### Is the RevClamp MCP Server server still maintained? RevClamp MCP Server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - Remote endpoint: https://api.revclamp.com/api/mcp - Repository: https://github.com/revclamp/revclamp-mcp - Changelog RSS feed: https://verifymcp.io/servers/revclamp-revclamp-mcp/api-mcp.xml - Changelog JSON feed: https://verifymcp.io/servers/revclamp-revclamp-mcp/api-mcp.json - HTML version of this page: https://verifymcp.io/servers/revclamp-revclamp-mcp/api-mcp