Ra Pay vs WavePay Payments
Ra Pay is an MCP server published by rapay.ai. Marketplaces we read that list it: 1 (Official MCP Registry). WavePay Payments is an MCP server published by t3ratech. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.2.5 Downloads/month (npm): 181 Downloads/week (npm): 44 Not marked · First seen |
Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Ra Pay | WavePay Payments |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@rapay/mcp-server) | Remote server (t3rnel-wavepay-production.t3ratech.workers.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/ra-pay-ai/rapay | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (35 h ago) |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Ra Pay
Send fiat payments via MCP with two-step confirmation and Stripe Connect.
WavePay Payments
Payments MCP: self-serve merchant key, PayNow + PayPal checkouts.
How to run each
Ra Pay As a local MCP server: npm package
claude mcp add --transport stdio ra-pay -- npx -y @rapay/mcp-serverWavePay Payments As a remote MCP server
claude mcp add --transport http wavepay https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp --header "x-wavepay-service-key: <YOUR_X_WAVEPAY_SERVICE_KEY>"Requires: x-wavepay-service-key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only WavePay Payments has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Ra Pay · What it can do: WavePay Payments · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.