Loomal

Monetize your Communication MCP server every message has a carrier cost. Pass it through.

SMS, WhatsApp, email, chat — communication servers sit on rails that charge per message. x402 lets you bill the agent the same way the carrier bills you, one call at a time.

Communication is the rare MCP category where upstream billing is already per-unit. Carriers charge per SMS, WhatsApp's business platform charges per conversation, email providers charge per send. Servers like mcp-zenvia (SMS, WhatsApp, RCS), mcp-evolution-api (WhatsApp messaging and instances), and Agenticmail MCP (real email and SMS for agents) absorb those costs on every outbound call.

Passing per-unit costs through a free endpoint is a losing trade. x402 aligns the books: the agent pays in USDC before the message sends, settlement lands on Base in roughly two seconds, and your margin is whatever you set above the carrier rate.

Why messaging is the easiest pricing story on the index

Most categories have to argue about what a call is worth. Messaging doesn't — the carrier already told you. An SMS has a market rate; a WhatsApp template message has a published price; a deliverability-managed email send has a known cost. Your per-call price is cost plus margin, and any agent operator can verify the math.

Volume strengthens the case rather than weakening it. An agent running notification campaigns through a notifykit-style multi-provider tool sends thousands of messages; at thousands of calls, even a one-cent margin per send is real revenue, and x402's per-call settlement means none of it sits in receivables.

Pricing logic: sends, reads, and inbox capabilities

Outbound sends carry the carrier pass-through: price each send tool at your unit cost plus margin, by channel — SMS, WhatsApp, RCS, and email each get their own price since each has its own cost basis. Loomal's $0.01 minimum sets the floor for the cheapest channels.

Reads and searches are infrastructure-priced rather than carrier-priced: retrieving threads through a Slack Explorer-style tool or querying an IMAP inbox via an email-mcp deployment costs you connection upkeep, not per-unit fees — a cent or two per query fits. The premium tier is stateful capability: a provisioned inbox that can receive verification codes, an always-connected WhatsApp instance, multi-account IMAP IDLE monitoring. Those tools hold expensive long-lived state and justify markedly higher per-call prices.

Claiming your slice of 143 live servers

Communication has 143 live listings on the Loomal index, most unclaimed and unpriced. Claiming yours is a GitHub ownership verification; pricing is a per-tool field in the console you can revise as carrier rates move — one field, no redeploy.

The x402 middleware sits in front of your remote endpoint: unpaid calls get an HTTP 402 with the price, paid calls send the message and return an Ed25519-signed receipt with the Base transaction hash. Since payment precedes execution, you never eat a carrier fee for a caller who didn't pay. Loomal's 5% fee on settled transactions is currently waived.

Spam economics work in your favor

Free messaging endpoints become spam cannons — it's why every free SMS gateway dies behind verification walls. A per-call price inverts the incentive: spam at $0.02 per message is unprofitable for spammers but trivial for legitimate agents confirming appointments or sending verification codes.

That protection has commercial value of its own. Your sender reputation, deliverability, and carrier relationships survive because the price filters traffic — making the paid endpoint more reliable than the free one could ever have stayed.

Frequently asked questions

How do I price message sends when carriers charge me per unit?

Cost-plus, per channel. Each send tool gets a price at or above your carrier rate for that channel — SMS, WhatsApp, RCS, and email priced separately. The agent pays in USDC via x402 before the message sends, so you never front a carrier fee for an unpaid call.

What about read operations like searching messages or threads?

Those carry infrastructure cost rather than carrier cost — connection upkeep, indexing, account state. A cent or two per query is typical, with Loomal's $0.01 minimum as the floor. Stateful capabilities like provisioned inboxes or live WhatsApp instances justify more.

Doesn't charging per message just push agents to free alternatives?

Free messaging endpoints don't stay open — they get spammed into verification walls or shut down. A priced endpoint stays reliable because the price filters abuse, and reliability is what an agent sending verification codes or appointment confirmations actually needs.

What's the setup path on Loomal?

Claim your server's listing, verify ownership through GitHub, set per-tool prices in the console, and deploy the x402 middleware in front of your remote endpoint. Loomal charges 5% on settled transactions, currently waived.

Run a Communication MCP server?

Claim your listing, set a per-call USDC price, and let AI agents pay for every call over x402.

List it on Loomal