AI agent payment security - spending limits, whitelists, and human approval.
AI agent payment security - spending limits, whitelists, and human approval. Exposed over MCP by the clawvault mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
MCP (Model Context Protocol) server for ClawVault - AI agent payment security layer.
Everything the assistant can do here goes through one of these:
request_payment — Request a payment through ClawVault. The payment will be evaluated against your security rulescheck_limits — Check if a payment would be allowed before making it. Returns whether it would auto-approve or need manual approvalget_payment_status — The get_payment_status tool exposed by this serverlist_transactions — The list_transactions tool exposed by this serverget_vault — Get vault status including wallet address, balances, and current spending limitsfreeze_agent — Emergency freeze an agent to block all its payment requestsYou will need 2 environment variables: CLAWVAULT_API_KEY, CLAWVAULT_API_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
The server ships on npm as clawvault-mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the payments and commerce group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Clawvault's toolset — request_payment, check_limits, get_payment_status and 3 more — is a fair guide to whether it matches your workflow. It is maintained by andrewszk; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| request_payment | Request a payment through ClawVault. The payment will be evaluated against your security rules. |
| check_limits | Check if a payment would be allowed before making it. Returns whether it would auto-approve or need manual approval. |
| get_payment_status | The get_payment_status tool exposed by this server. |
| list_transactions | The list_transactions tool exposed by this server. |
| get_vault | Get vault status including wallet address, balances, and current spending limits. |
| freeze_agent | Emergency freeze an agent to block all its payment requests. |
{
"mcpServers": {
"clawvault": {
"command": "npx",
"args": ["-y", "clawvault-mcp-server"],
"env": {
"CLAWVAULT_API_KEY": "your-value",
"CLAWVAULT_API_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| CLAWVAULT_API_KEY | Credential the server authenticates with. | Yes |
| CLAWVAULT_API_URL | Endpoint or connection string the server talks to. | Yes |
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.