req-invoice-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REQUEST_PAYEE | No | Default wallet that gets paid. Used for create_invoice with an API key. | |
| REQUEST_ORIGIN | No | Origin matching the Client ID's allowed domain. Required when using REQUEST_CLIENT_ID. | |
| REQUEST_API_KEY | No | Request Network API key credential. Required unless REQUEST_CLIENT_ID is provided. | |
| REQUEST_API_URL | No | API base URL. | https://api.request.network |
| REQUEST_CLIENT_ID | No | Request Network Client ID credential. Required unless REQUEST_API_KEY is provided. | |
| REQUEST_DESTINATION_ID | No | Your dashboard Route ID. Enables create_payment_link. |
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 |
|---|---|
| create_payment_linkA | Bill someone and get a link they can open to pay in their own wallet. Uses the network and token of the receiving route set up in the Request Network dashboard (REQUEST_DESTINATION_ID). The amount is in that route's token. This is the easiest way to get paid. |
| create_invoiceA | Create an on-chain invoice (a "request") for a specific amount, currency and network. paymentCurrency picks the token and network, e.g. "USDC-base", "USDC-mainnet", "ETH-sepolia-sepolia" (use find_currency to look IDs up). invoiceCurrency is what the amount is denominated in; it defaults to paymentCurrency, or use "USD" to bill a dollar amount paid in crypto. Returns the invoice ID. |
| check_invoiceB | Check whether an invoice has been paid, with the payment transaction(s) if it has. |
| list_invoicesB | List invoices created with these credentials, newest first, with paid/unpaid status. |
| get_payment_transactionsA | For the PAYER: returns the unsigned transaction(s) needed to pay an invoice (a token approval, if needed, then the payment). This server never signs or sends anything; the payer reviews and signs them in their own wallet. |
| find_currencyA | Look up Request Network currency IDs to use as paymentCurrency, e.g. symbol "USDC" on network "base" or "sepolia". |
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 6 tools
Each tool has a reasonably distinct role, but create_invoice and create_payment_link both 'bill someone' and could be confused at first glance, and get_payment_transactions vs check_invoice both surface payment transactions from different perspectives (payer vs payee). The descriptions do clarify these boundaries well, keeping overlap low.
All names are snake_case verb_noun, which is consistent. Minor deviation in verb choice for reads (get_payment_transactions, find_currency, check_invoice, list_invoices) rather than a single read verb, but the pattern remains predictable.
Six tools is a well-scoped surface for an invoicing server: create, pay, look up currency, check status, and list. Each tool clearly earns its place with no filler.
The core lifecycle (create invoice/link, obtain payment transactions, check paid status, list) is covered. Gaps remain around canceling/voiding an invoice, retrieving full invoice details by ID, and refunds, but agents can work around these for the primary pay-and-verify flow.