Mifactory Payments

io.github.mifactory-botPublished by GitHub account mifactory-botv1.0.0Updated Oct 24, 2026

Stripe payments for AI agents. Create links, verify, manage customers.

The publisher's own server: Payments Ai Mcp

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that lets an assistant create Stripe payment links, verify payments, create customers and list recent payments, charging credits per call.

What you can do
Create Stripe payment links for a charge (10 credits per call). Verify whether a payment has been completed (5 credits). Create customers in Stripe (5 credits). List recent payments from the connected Stripe account (3 credits).
When to use it
Useful when an assistant needs to handle Stripe payments on the user's behalf: generating payment links, checking whether a payment went through, adding customers, or reviewing recent payments.
Requirements
A remote endpoint at mifactory-payments.vercel.app over streamable HTTP; no authentication, environment variables or headers are declared. A Stripe account is implied by the tools, and each tool call consumes credits.
Before you install
Every tool call spends credits (10, 5, 5 and 3 respectively), so usage has a cost. The tools create payment links and customers and read payment data in the user's Stripe account, which are write and read actions on real financial data. No authentication is declared, so how the server reaches the user's Stripe account is unclear; confirm this before connecting.

Installation

In SourceWeft

  1. Open Mifactory Payments in the dashboard and add it to a workspace.
  2. 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.github.mifactory-bot%2Fmifactory-payments/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": {
    "mifactory-payments": {
      "type": "http",
      "url": "https://mifactory-payments.vercel.app/mcp"
    }
  }
}

README

This repository has no README.

Tools

4

verify_payment

Verifica si un pago fue completado. Cuesta 5 créditos.

Parameterssession_idrequiredstripe_keyrequired

create_customer

Crea un cliente en Stripe. Cuesta 5 créditos.

Parametersnameemailrequiredmetadatastripe_keyrequired

list_payments

Lista los pagos recientes de tu cuenta Stripe. Cuesta 3 créditos.

Parameterslimitstripe_keyrequired

Version history

1
  1. v1.0.0LatestSep 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Payments integrations