mppx
TypeScript SDK for the Payment HTTP Authentication Scheme. Handles 402 Payment Required flows with Tempo, Stripe, and other payment methods. Use when integrating payments or mppx into a client or server application.
How do I install this agent skill?
npx skills add https://github.com/tempoxyz/mpp --skill mppxIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The mppx skill is a TypeScript SDK designed for handling HTTP 402 payment flows via Tempo and Stripe. The skill adheres to security best practices, such as recommending environment variables for secret management and using reputable libraries. No malicious patterns or security risks were identified.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
mppx
TypeScript SDK for the "Payment" HTTP Authentication Scheme. Full 402 flow: challenge → credential → receipt.
What I can accomplish
- Add
402payment handling to a client withFetch.polyfillorFetch.from. - Protect HTTP routes with server-side MPP Challenges and Receipt responses.
- Accept one-time Tempo stablecoin payments with
tempo.charge. - Accept metered Tempo stablecoin payments with
tempo.session. - Accept one-time card payments with
stripe.charge. - Verify Credentials directly for custom transports or background workflows.
- Wrap MCP clients and servers so tool calls can require payment.
Required inputs
- Client integrations need a signing account and one or more client payment methods.
- Server integrations need a recipient, amount, and
MPP_SECRET_KEY. Tempo currency lists are optional. - Tempo examples use chain ID
4217unless a page explicitly covers Moderato testnet. - Stripe examples need a configured Stripe account and Shared Payment Token flow.
- MCP integrations need the MCP client or server object to wrap.
Constraints
- Keep
MPP_SECRET_KEYserver-side and out of logs. - Never commit private keys or wallet seeds.
- Treat runtime
402Challenges as authoritative for current payment terms. - Return
idandopaqueunchanged when responding to a Challenge. - Use OUSD in single-currency Tempo examples. Omit
currenciesto offer OUSD first with network-specific fallbacks. - Factory
currenciesconfigures accepted tokens; wire requests and per-handler overrides retain singularcurrency. - Use complete token addresses. Preserve provider-specific token requirements.
Client
import { Mppx, tempo } from 'mppx/client'
// Polyfills globalThis.fetch to handle 402 automatically
Mppx.create({
methods: [tempo({ account })],
})
const res = await fetch('https://api.example.com/resource')
Without polyfilling:
const mppx = Mppx.create({
methods: [tempo({ account })],
polyfill: false,
})
const res = await mppx.fetch('https://api.example.com/resource')
Server
import { Mppx, Store, tempo } from 'mppx/server'
import { privateKeyToAccount } from 'viem/accounts'
const account = privateKeyToAccount('0x...')
const mppx = Mppx.create({
methods: [
tempo.charge({ recipient: '0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266' }),
tempo.session({
account,
chainId: 4217,
recipient: '0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266',
store: Store.memory(),
}),
],
secretKey: process.env.MPP_SECRET_KEY,
})
async function handler(request: Request): Promise<Response> {
const result = await mppx.charge({ amount: '1.00' })(request)
if (result.status === 402) return result.challenge
return result.withReceipt(Response.json({ data: '...' }))
}
Methods
| Method | Intent | Description |
|---|---|---|
tempo.charge | charge | One-time stablecoin payment (TIP-20 token transfer on Tempo) |
tempo.session | session | Streaming payments via payment channels on Tempo |
stripe.charge | charge | One-time payment via Stripe |
Server tempo() returns a charge/session pair per accepted currency. Individual server tempo.charge() and tempo.session() factories return nonempty method arrays for their intent. Mppx.create flattens these groups. Mainnet defaults to OUSD then USDC.e; Moderato defaults to OUSD then pathUSD. Pass currencies to replace that list, for example currencies: ['0x20c0000000000000000000006a37DA5C996874BE'] to accept only OUSD.
Exports
| Path | Purpose |
|---|---|
mppx | Core primitives (Challenge, Credential, Method, Receipt, PaymentRequest) |
mppx/client | Mppx, tempo, stripe, session, Transport |
mppx/server | Mppx, tempo, stripe, Transport, Store, NodeListener |
mppx/hono | Hono middleware |
mppx/express | Express middleware |
mppx/nextjs | Next.js middleware |
mppx/elysia | Elysia middleware |
CLI
mppx includes a CLI for making paid requests during development:
npx mppx account create # create wallet
npx mppx mpp.dev/api/ping/paid # make paid request
npx mppx example.com -v # verbose output
References
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/tempoxyz/mpp/mppx">View mppx on skillZs</a>