infinitepay-checkout
CloudWalk publishes NO MCP server. Searches of the MCP registries, npm (@modelcontextprotocol and CloudWalk/InfinitePay scopes), the CloudWalk GitHub organization and the InfinitePay developer pages all missed, and no /.well-known/oauth-protected-resource or agent card exists on any host. The tools below are a CANDIDATE surface derived mechanically from the two operations in the captured OpenAPI — what an MCP server for the InfinitePay Checkout API would expose if one existed. Because no server exists, NO `MCPServer` pointer is wired in apis.yml: emitting one would credit CloudWalk with an agent surface it does not operate.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Descriptor
Candidate descriptor · transport
Tools
create_checkout_link— Create an InfinitePay hosted checkout payment link for a basket of items and return the URL to send the buyer to.check_payment_status— Check whether an InfinitePay checkout link has been paid, and with what amount, installments and capture method.
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.