Authoryze
ai.authoryzePublished by authoryze.aiOfficial publisherv1.0.1Updated Oct 24, 2026
Give your AI agent a spending limit: approval controls and single-use virtual cards.
Overview
Remote MCP server that lets an AI agent request purchases under spending limits, with owner approval and single-use virtual cards.
- What you can do
- Request a purchase from a named merchant for a given amount with a reason, and receive approval, denial, or a safe-to-retry failure
- Check the status of a purchase request without exposing card details
- Review spending against daily, weekly, monthly, total and account-wide limits
- Retrieve the card number, expiry and security code once for an approved purchase
- When to use it
- Use it when you want an agent to be able to pay for things online without giving it your own card details, and you want each purchase gated by limits and your approval.
- Requirements
- Remote endpoint at authoryze.ai over streamable HTTP. OAuth-capable clients authenticate via OAuth 2.1 with PKCE and dynamic client registration; other clients need a static agent API key sent as an Authorization bearer token. Only US-issued cards are supported.
Installation
In SourceWeft
- Open Authoryze in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ai.authoryze%2Fauthoryze/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"authoryze": {
"type": "http",
"url": "https://authoryze.ai/api/mcp"
}
}
}README
Authoryze MCP Server
Authoryze gives your AI agent a spending limit. It lets you hand an agent a payment method without handing it your card: you define what it can buy, from which merchants, and up to what amount, and every purchase request comes to you for approval before a single-use virtual card is issued. It is built on Visa Intelligent Commerce and Mastercard Agent Pay, and is currently available for US-issued cards. Authoryze is a remote MCP (Model Context Protocol) server that works with Claude, Claude Code, ChatGPT, Cursor, Windsurf, and any MCP-compatible client.
Installation
OAuth-capable clients such as Claude and ChatGPT need only the endpoint:
Clients that don't support OAuth, such as Claude Code, Codex, and custom frameworks, authenticate with a static agent API key as a bearer token:
Tools
- request_purchase - Ask to make a purchase from a specific merchant, for a specific amount, with a reason. The request either gets approved automatically, gets sent to the account owner for approval, gets denied with a reason, or fails in a way that's safe to retry.
- check_status - Look up what happened to a purchase request: approved, denied, still waiting on approval, or failed. Doesn't reveal any card details itself.
- get_spending_summary - See how much has been spent so far against the configured limits (daily, weekly, monthly, and total), including any account-wide limit that applies across all of an account's agents.
- retrieve_card - Once a purchase is approved, get the actual card number, expiry, and security code to complete the purchase. This can only be done once per approved purchase; the details are shown a single time and can't be retrieved again.
Requirements
Authoryze is available for US-issued cards only. International support is pending issuer coverage on the agentic token programs.
Authentication requires either OAuth 2.1 with PKCE (S256) and Dynamic Client Registration, or a static agent API key used as a bearer token.
Links
Homepage: https://authoryze.ai
Docs: https://authoryze.ai/docs
Smithery
Listed on Smithery: https://smithery.ai/servers/authoryze/authoryze
Source: README.md at commit a7db8e4
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.