m2m-monster
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_pricingB | Agent-to-agent fee formula, referral program and the whitelisted token mints of this network. |
| quote_paymentB | Price a payment to a payee: gross amount, net amount to the payee, fee_gross, discount, fee_net, treasury, mint and a 30-second expiry. Returns a signed quote. |
| build_paymentA | Build the m2m-split transaction for a quote: the payer's transfer to the payee and the USDC fee transfer to the treasury, in one atomic transaction where the payer pays its own gas. Checks that the receiving token accounts exist and that the payer holds USDC for the fee, and simulates it. Unsigned. Sign it locally with your own Solana key; m2m.monster never sees or uses agents' private keys. |
| verify_paymentA | For the payee: check a payer-signed transaction against its quote (net amount, fee to the treasury, whitelisted mints, quote id and expiry) and simulate it before submitting. |
| submit_paymentA | Broadcast a transaction the payer already signed, wait for confirmation and return the signed receipt. Only broadcasts; never signs or pays payment transactions. A retry with the same idempotency_key never pays twice. |
| verify_receiptB | Verify a receipt: the m2m.monster signature and that the confirmed on-chain transaction matches it. |
| build_refundA | Build a refund from the payee back to the payer, linked to the original receipt. The payee signs it and pays its gas; it has no m2m.monster fee and the original fee is not returned. Unsigned. Sign it locally with your own Solana key; m2m.monster never sees or uses agents' private keys. |
| register_agentA | Optional registration; paying and getting paid work without it. It unlocks referral credits and receipt history. Call once without |
| get_referral_statusA | Your referrer, referred agents, credits and their expiry dates. Credits are discounts on your own fees, never cash. Requires the api_key from register_agent. |
| get_statusB | Service status and API version. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
The tools map cleanly to distinct payment lifecycle stages: pricing, quoting, building, verifying, submitting, receipt verification, and refunds. The main possible confusion is between verify_payment and verify_receipt, but their contexts (pre-submit transaction vs confirmed receipt) are adequately differentiated.
All tool names use consistent snake_case with a clear verb_noun pattern such as get_pricing, quote_payment, build_payment, verify_payment, and submit_payment. The minor use of quote_ as a verb is still readable and consistent with the overall convention.
Ten tools are well-scoped for an agent payment server, with each tool covering a meaningful step in the quote-build-verify-submit-receipt-refund flow. Supporting tools for pricing, registration/referrals, and status are also justified without bloating the surface.
The core payment lifecycle is well covered, including fee discovery, quote creation, transaction building, verification, submission, receipt verification, and refunds. Minor gaps remain around retrieving receipt history or listing past payments, despite registration being described as unlocking receipt history.