Kifly — Agentic Commerce & Payments

io.kiflyPublished by kifly.ioOfficial publisherv1.1.4Updated Oct 24, 2026

Multi-seller shopping for AI agents. Settle via Stripe MPP or x402 USDC on Base. Hosted.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Kifly is a hosted MCP endpoint that lets an AI assistant shop across multiple sellers and settle purchases through Stripe MPP or x402 USDC on Base.

What you can do
Browse and shop across multiple sellers' catalogs from within an assistant session, scoped to the seller or network tied to the API key in use. Complete purchases using Stripe MPP or x402 USDC on Base as the settlement path. Operate as a hosted remote service, so no local package or runtime is involved.
When to use it
Use it when an assistant needs to find and buy goods from multiple sellers and complete payment programmatically, rather than only researching products.
Requirements
A remote connection to the Kifly hosted endpoint over streamable HTTP. A bearer agent API key, issued from the Kifly seller portal, sent in the Authorization header; the key determines which catalog scope is visible. Network access to the endpoint.
Before you install
The server handles real payments, so purchases may spend money through Stripe MPP or x402 USDC on Base. The bearer API key is a live credential and should be kept secret. Catalog scope is fixed by the key, so a key issued for one seller or network will not see others.

Installation

In SourceWeft

  1. Open Kifly — Agentic Commerce & Payments in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. 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/io.kifly%2Fmcp/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "kifly-agentic-commerce-payments": {
      "type": "http",
      "url": "https://kifly.io/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.1.4LatestSep 16, 2026

Score

39% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.