verify_payment_requirements — aml MCP Tool
verify_payment_requirements
(verify payment requirements) is one of 10 tools on the
aml
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call verify_payment_requirements from your client
- Claude Code aml verify_payment_requirements run in your project directory
- Claude Desktop aml verify_payment_requirements ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor aml verify_payment_requirements ~/.cursor/mcp.json
- VS Code aml verify_payment_requirements .vscode/mcp.json
- Zed aml verify_payment_requirements ~/.config/zed/settings.json
- Windsurf aml verify_payment_requirements ~/.codeium/windsurf/mcp_config.json
- Cline aml verify_payment_requirements ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI aml verify_payment_requirements ~/.gemini/settings.json
- Grok aml verify_payment_requirements .mcp.json (in your project root)
- ChatGPT aml verify_payment_requirements Settings → Connectors → Advanced → Developer mode
- Claude.ai aml verify_payment_requirements Settings → Connectors → Add custom connector
- LangChain aml verify_payment_requirements pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http aml https://oceanalt.com/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.