Skip to main content
Glama
RevClamp MCP Server

RevClamp MCP Server

Official

Related Servers

Alternatives to RevClamp MCP Server

  • A
    license
    Not graded
    quality
    C
    maintenance
    The Stripe Model Context Protocol server allows you to integrate with Stripe APIs through function calling. This protocol supports various tools to interact with different Stripe services.
    31,367 npm
    2,068
    -

Related Servers

  • A
    license
    B
    quality
    B
    maintenance
    RevClamp MCP Server & CLI for Stripe 2025-03-31.basil entitlement checks, Visa CE 3.0 dispute staging, EU/XI VIES VAT validation, Shopify Plus B2B Net-15/30/60 reconciliation, HMAC checks, and 72h replay simulation.
    9
    1,238 npm
    1
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Per-call billing and metering proxy for MCP tool servers. Providers set pricing via the open MCP Billing Spec (MIT), consumers pay through Stripe Connect with signed receipts and SLA monitoring.
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Stdio proxy for HirePulse: 27 live tools for company research, hiring, job changes, public contacts and commerce evidence. Focused remote profiles: 9 B2B or 11 commerce tools. Free sandbox, 10 successful calls per agent per UTC day (shared network ceiling), and eligible 25-call trials. Paid results use x402 USDC on Base. Install: npx -y hirepulse-mcp (Node.js 20+).
    26
    49 npm
    1
    MIT
  • F
    license
    Not graded
    quality
    D
    maintenance
    Paid remote MCP server enabling CLI tool execution with structured receipts, usage logs, and audit-ready evidence for agent and CI workflows.
    1
    -

TDQS

B3.4/5.0

Scored across 9 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityNo data
ResponsivenessSyncing