Local MCP server/Finance

GenesisPay MCP server

Local MCP server

GenesisPay lets an agent pay x402 APIs in USDC on Base from an agent wallet, within owner-set limits. Requests above the limit wait for approval. The provider distributes a local stdio MCP server as @genesis-tech/genesispay-mcp and requires GENESISPAY_AGENT_KEY plus the wallet environment variables it documents. Payments are paused, so payment tools currently return 503 payments_disabled.

Agent key (GENESISPAY_AGENT_KEY) Source checked Nov 12, 2026 Local install path Reviewed 2026-11-16
About

Where it fits

Agent developers who need controlled x402 payments from a wallet with owner-set limits.

  • Set owner limits for agent spending.
  • Pay an x402 API in USDC after a limit check.
  • Approve a payment above the limit.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Local stdio server

The provider README documents the npm stdio package. Set GENESISPAY_AGENT_KEY and the wallet variables it requires in the client environment.

claude mcp add genesispay -- npx -y @genesis-tech/genesispay-mcp

This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • The client cannot find the vomo command. Confirm the global CLI install and that the executable is on PATH.
  • The process starts but no tools appear. Sign in to the provider CLI, restart the client, and check the local command output for errors.
Safety

Before you connect

Local process, your machine
  • The MCP server process runs on your machine, not on a provider host.
  • Data leaves only through the model provider and any MCP servers you attach.
  • Review the local command, package, and files it can reach before running it.
  • Stop the process or remove the client entry when you no longer need it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

GenesisPay documentationhttps://genesispay.finance/docs/mcp#web-chatGitHub repositoryhttps://github.com/GenesisTechAT/genesispay-js