Glossary

What is an MCP server?

An MCP server exposes tools, resources and prompts to AI applications over the Model Context Protocol. What that means for payment tools.

An MCP server is a service that offers tools, resources or prompts to AI applications using the Model Context Protocol, an open protocol built on JSON-RPC 2.0.

How does it work?

The MCP specification describes three roles: hosts are the AI applications that start connections, clients are the connectors inside them, and servers provide context and capabilities. A server can offer resources (data), prompts (templates) and tools (functions the model can call). Servers run either locally, talking to the host over stdio, or remotely over HTTP. Tools are model-controlled: the model decides when to call them based on the conversation. That is why the specification says there should always be a human in the loop able to deny tool invocations, and why servers must validate inputs, apply access controls and rate-limit calls.

In practice

You add a server to a host such as Claude Code, Cursor, Codex or Claude Desktop with a URL and credential, or a command to run. The host lists its tools to the model. For a payment server, the tools might be get_budget to read remaining allowance and create_payment to request a payment; the server, not the model, decides whether each payment goes through. Before you trust a server, list its tools and read their descriptions and input schemas: that is everything the model will be able to ask it to do.

What it does not mean

  • An MCP server is not an AI model. It's the thing the model calls.
  • Connecting a server doesn't grant it access to everything in your chat; it receives the tool calls the host sends it.
  • Tool annotations a server publishes are hints. The spec says clients must treat them as untrusted unless the server is trusted.

Where does Veyra fit?

Veyra is a hosted MCP server at https://veyra.money/api/mcp, authenticated with a bearer token, with seven tools: get_capabilities, get_budget, list_payment_sources, create_payment, get_payment, list_payments and cancel_payment. For hosts that can't send a header, the open-source veyra-mcp package is a local stdio bridge that relays calls to it.

Sources

Guides that use this term

This page explains how agent payments and the related technology work. It is not financial, investment, legal or tax advice. Protocols and provider features change; check the linked official sources before relying on a detail.