Finance · Remote MCP server
WavePay Payments
Payments MCP: self-serve merchant key, PayNow + PayPal checkouts.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.t3ratech/wavepay- Version
- 1.0.0
- Status
- Active
- Category
- finance
- Transport
- Streamable HTTP
- Published
- 2026-09-27
- Updated
- 2026-09-27
- Publisher
- t3ratech (GitHub) · 3 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/t3ratech) · how
- Listed under
- PayPal MCP servers
- Website
- wavepay.t3ratech.co.zw
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp | x-wavepay-service-key (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- wavepay 2 · protocol 2025-03-26
- Tools discovered
- 6:
wavepay_register,wavepay_providers,wavepay_pricing,wavepay_checkout,wavepay_checkout_status,wavepay_catalog - Checked on
- 2026-10-05
How to connect WavePay Payments
WavePay Payments is a remote MCP server: there is nothing to install. Its endpoint is https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: x-wavepay-service-key (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from t3ratech (GitHub)
| Server | Runs |
|---|---|
| Market PulseEvidence index for AI agent work - lane grades, evidence, jobs. | Remote · HTTPLive check: ✓ handshake |
| MCP Session BridgeDrive a browser you are already signed into, through the free T3rnel Browser extension. | Local · stdio |
More finance servers
| Server | Runs |
|---|---|
| WasselMENA commerce integration layer for AI agents: payments, BNPL, logistics, e-commerce, tax. | Remote · HTTPLive check: sign-in required |
| WatchdogWho can change a Solana program or EVM contract, dependency advisories, scans. Paid per call (x402). | Local · stdio |
| WathbaSaudi payments, OTP/SMS, KYC, ZATCA e-invoicing and shipping for AI coding agents. | Remote · HTTPLive check: sign-in required |
| WattCoinAgents earn WATT on Solana: register with no wallet, claim tasks, build a reputation score. | Remote · HTTPLive check: ✓ handshake |
| Wealth Engine - Economic Opportunity IntelligenceRanked economic opportunities, market evidence, experiments, and margin intelligence for AI agents. | Remote · HTTPLive check: ✓ handshake |
| wealthapi.euRead-only MCP server for wealthAPI: portfolio, cash-flow, and dividend insights for AI assistants. | Local · stdio |
| WealthnowRead-only market data for agents: prices, fundamentals, filings, options, credit, private markets. | Remote · HTTPLive check: sign-in required |
| WealthosPlan your financial future with AI: track net worth, manage budgets, and forecast scenarios. | Remote · HTTPLive check: sign-in required |