mcpField
P

pay-mcp

Local
@vauban.techFinance

About pay-mcp

x402 pay tools for MCP clients, plus a `buy` command: read the offer, consent, pay. Starknet, Base.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"tech-vauban-pay": {
"command": "npx",
"args": [
"-y",
"@vauban-pay/mcp"
],
"env": {
"STARKNET_RPC_URL": "<STARKNET_RPC_URL>",
"PAY_MCP_SEPOLIA_ACCOUNT_ADDRESS": "<PAY_MCP_SEPOLIA_ACCOUNT_ADDRESS>",
"PAY_MCP_SEPOLIA_PRIVATE_KEY": "<PAY_MCP_SEPOLIA_PRIVATE_KEY>",
"PAY_MCP_STANDARD_X402_PAYEES": "<PAY_MCP_STANDARD_X402_PAYEES>",
"PAY_MCP_STANDARD_X402_MAX_WEI": "<PAY_MCP_STANDARD_X402_MAX_WEI>",
"PAY_MCP_STANDARD_X402_ACCOUNT_ADDRESS": "<PAY_MCP_STANDARD_X402_ACCOUNT_ADDRESS>",
"PAY_MCP_STANDARD_X402_PRIVATE_KEY": "<PAY_MCP_STANDARD_X402_PRIVATE_KEY>",
"PAY_MCP_EVM_KEYSTORE_PATH": "<PAY_MCP_EVM_KEYSTORE_PATH>",
"PAY_MCP_EVM_PASSWORD_PATH": "<PAY_MCP_EVM_PASSWORD_PATH>",
"PAY_MCP_EVM_NETWORKS": "<PAY_MCP_EVM_NETWORKS>",
"PAY_MCP_EVM_PAYEES": "<PAY_MCP_EVM_PAYEES>",
"PAY_MCP_EVM_MAX_PER_PAYMENT": "<PAY_MCP_EVM_MAX_PER_PAYMENT>",
"PAY_MCP_EVM_MAX_PER_SESSION": "<PAY_MCP_EVM_MAX_PER_SESSION>",
"PAY_MCP_EVM_I_ACCEPT_MAINNET_SPEND": "<PAY_MCP_EVM_I_ACCEPT_MAINNET_SPEND>",
"PAY_MCP_EVM_ASSETS": "<PAY_MCP_EVM_ASSETS>"
}
}
}
}
Run commandnpx -y @vauban-pay/mcp
Environment variables to set
STARKNET_RPC_URLStarknet RPC endpoint. Optional. The buy command contacts no node unless you name one (a Starknet mainnet node; the chain it serves must then be the offer's). The chain-reading tools default to a public node not operated by Vauban.
PAY_MCP_SEPOLIA_ACCOUNT_ADDRESSStarknet Sepolia account address for make_payment signer mode. Optional; without it make_payment uses the sponsored mode, which calls the sponsor over the network and settles a real Sepolia transfer it funds.
PAY_MCP_SEPOLIA_PRIVATE_KEYSecretPrivate key for that account. Optional; never required to try the tools.
PAY_MCP_STANDARD_X402_PAYEESStandard x402 path (Starknet): comma-separated payTo addresses pay_for_resource may pay. Empty pays nobody (fail closed). * pays any payee: avoid it.
PAY_MCP_STANDARD_X402_MAX_WEIStandard x402 path: cap on one payment in atomic units (default 0.1 STRK).
PAY_MCP_STANDARD_X402_ACCOUNT_ADDRESSStandard x402 path: a signer of its own (falls back to PAY_MCP_SEPOLIA_*).
PAY_MCP_STANDARD_X402_PRIVATE_KEYSecretPrivate key for that account. Optional.
PAY_MCP_EVM_KEYSTORE_PATHSecretEVM path: path to your Web3 Secret Storage v3 keystore. Never a key in the environment.
PAY_MCP_EVM_PASSWORD_PATHSecretEVM path: path to the file holding that keystore's password.
PAY_MCP_EVM_NETWORKSEVM path: comma-separated CAIP-2 networks pay_for_resource may pay on, e.g. eip155:84532. Empty pays nothing (fail closed).
PAY_MCP_EVM_PAYEESEVM path: comma-separated payTo addresses pay_for_resource may pay. Empty pays nobody (fail closed). * pays any payee, up to the session cap: avoid it.
PAY_MCP_EVM_MAX_PER_PAYMENTEVM path: cap on one payment, in atomic units of the asset (1000000 = 1 USDC). No default: unset refuses.
PAY_MCP_EVM_MAX_PER_SESSIONEVM path: cap on the total value of the signed authorizations this process hands over, per network and asset, never credited back. No default: unset refuses.
PAY_MCP_EVM_I_ACCEPT_MAINNET_SPENDEVM path: comma-separated CAIP-2 value networks you consent to spend real money on, each named (e.g. eip155:8453). Required for any network other than Base Sepolia and Ethereum Sepolia.
PAY_MCP_EVM_ASSETSEVM path: comma-separated <CAIP-2>/<token address> entries payable. Default: the network's known USDC only.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@vauban-pay/mcp0.19.0

Tools

6

Saved tool list · updated 5d ago

ParameterTypeRequiredDescription
json_objectobjectYesThe JSON object to canonicalize and hash.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.