VibeCart

Name: VibeCart
Author: runjohnray2-lgtm

by runjohnray2-lgtmversion 0.3.0i★ –iRuns in the cloud

Registry nameio.github.runjohnray2-lgtm/vibecart

Install

Overview

Description from the maker (original English)

Agent-native commerce with trusted catalog, durable carts, and Stripe Checkout via MCP and UCP.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiVery new★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Online shops & payments

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://vibecart.vercel.app/mcp

Run this in your terminal

claude mcp add --transport http vibecart https://vibecart.vercel.app/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "vibecart": {
      "url": "https://vibecart.vercel.app/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "vibecart": {
      "type": "http",
      "url": "https://vibecart.vercel.app/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://vibecart.vercel.app/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account runjohnray2-lgtm, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Online shops & paymentsi

More stars than 0% of the other 2555 servers in this category
Published to the registry more recently than 26% of the other 2555 servers in this category
Basic checks equal to or better than 100% of the other 2555 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is VibeCart safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.0) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spree Commerce: open-source B2B and marketplace ecommerce

Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.

by spreeWidely used★ 15.8KUpdated 9 days ago

Runs in the cloud

Install

Stripe MCP

Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.

by stripeGrowing★ 2KUpdated 12 months ago

Runs in the cloud✓ stripe.com

Install

MCP Cn Commerce

8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending

by TonyWang-hubEarly↓ 73/wk★ 96Updated 29 days ago

Runs on your computer

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

VibeCart

Commerce infrastructure for AI-built apps and AI agents.

VibeCart lets a merchant keep their existing app and Stripe account while adding a small, inspectable commerce layer that AI agents can discover and use. Payments settle directly to the merchant's Stripe account; VibeCart does not need to become merchant of record.

The architecture is protocol-first: one trusted commerce backend, then thin MCP/UCP/client adapters around it.

Live production surface

Generic MCP

Endpoint: https://vibecart.vercel.app/mcp

Tools:

vibecart.list_products
vibecart.get_product
vibecart.get_integration_instructions
vibecart.create_checkout

vibecart.create_checkout supports both the legacy single-product input and a trusted multi-item items[] input. Product prices are resolved on the server; callers do not supply real transaction prices.

Generic MCP clients should use /mcp.

Durable cart

VibeCart's Neon-backed cart is live in production:

POST /api/cart
GET /api/cart/:id
PATCH /api/cart/:id
DELETE /api/cart/:id
POST /api/cart/:id/checkout

The cart uses trusted server-side repricing, idempotent creation, optimistic version checks, expiration, multi-item state, and cart-to-Stripe Checkout handoff.

UCP

Discovery: https://vibecart.vercel.app/.well-known/ucp
UCP-aware MCP transport: https://vibecart.vercel.app/ucp/mcp
Released protocol target: UCP 2026-04-08

Production advertises released catalog and cart capabilities. Current cart tools are:

create_cart
get_cart
update_cart
cancel_cart

UCP calls require meta.ucp-agent.profile and capability negotiation. Do not point an ordinary MCP client at /ucp/mcp.

The order pipeline and released-schema get_order adapter also exist, but get_order remains hidden until its VibeCart Cloud lookup and real merchant permalink dependencies are configured. VibeCart does not advertise optional capabilities before their runtime dependencies are ready.

Stripe checkout and orders

Trusted multi-line Stripe Checkout creation is supported.
Stripe webhook signatures are verified before paid events enter the post-payment pipeline.
Delayed-payment completion is handled separately so orders are not created prematurely.
Paid Checkout line items are normalized into durable order records when VibeCart Cloud forwarding is configured.
Trusted merchant product IDs survive Checkout through Stripe Product metadata.

He Said Nothing physical-store pilot

/he-said-nothing is the controlled physical-product pilot for the $39, $59, and $89 mystery gift boxes. The storefront can remain public while ordering fails closed. When the full launch gate is configured it:

saves the relationship quiz, sizing clues, packaging choice, gift message, and fulfillment note in a durable cart
opens a cart-bound, idempotent Stripe Checkout Session
collects email, phone, shipping address, a separately disclosed shipping charge, and optional Stripe automatic tax
stores the verified paid order, line items, delivery details, gift clues, and event history in Neon
exposes paid orders only through the HMAC-signed merchant session at /he-said-nothing/admin
supports the fulfillment states New, Packing, Shipped, Cancelled, and Refunded-in-Stripe

The checkout gate requires every dependency in .env.example; HSN_CHECKOUT_ENABLED=true alone is insufficient. Test and live Stripe keys must match HSN_CHECKOUT_MODE, and live mode additionally requires customer-support, return-policy, and processing-time text.

Merchant catalog source

The built-in lib/products.ts catalog is demo/reference data only. A real merchant can keep SKUs and prices outside VibeCart and point Core at a merchant-controlled HTTPS JSON feed:

VIBECART_CATALOG_URL=https://merchant.example/vibecart/catalog.json

VIBECART_MERCHANT_NAME="Example Merchant"

Optional when the feed is private:

VIBECART_CATALOG_BEARER_TOKEN=server-side-secret

Accepted response shape:

"products": [ { "id": "sku-123", "name": "Example product", "description": "Merchant-controlled product data", "priceCents": 4900, "image": "https://merchant.example/products/sku-123.jpg", "variant": "Optional variant" } ] }

An array of products at the document root is also accepted. id, name, and a non-negative integer priceCents are required; image URLs, when present, must use HTTPS.

The configured source is shared by generic MCP catalog/checkout, UCP catalog, and durable cart repricing. VibeCart validates the document, rejects duplicate IDs, caps response/product counts, blocks redirects/private-network targets, applies a short timeout, and caches healthy catalog data for 30 seconds. If VIBECART_CATALOG_URL is configured and the source is unhealthy or invalid, commerce operations fail closed; VibeCart does not silently fall back to demo products.

Normal SKU and price changes therefore do not require editing VibeCart TypeScript or redeploying Core.

Agent-client distribution

VibeCart does not build a different commerce engine for every model. OpenAI/Codex/ChatGPT, Claude, Gemini, VS Code, Cursor, and other MCP clients connect to the same backend.

See:

docs/integrations/agent-clients.md
integrations/mcp-clients.json
https://vibecart.vercel.app/mcp-clients.json

Provider adapters are CI-checked to keep Stripe/database/catalog secrets and duplicated commerce logic out of client configuration.

VibeCart Cloud

VibeCart Core is free to self-host. VibeCart Cloud is the optional $29/month managed layer for merchants that want VibeCart to operate the recurring plumbing.

Current Cloud capabilities include:

durable verified commerce events
durable normalized paid-order records and order history
server-to-server order lookup
signed merchant fulfillment webhooks
delivery history and bounded retries
monitoring/alerts and support workflows

Cloud workspace: https://vibecart-cloud-uupzkh.v2.appdeploy.ai/

Merchant checkout revenue still settles directly to the merchant's Stripe account. VibeCart takes no percentage of merchant sales.

Quick start

npm install

npm run dev

Without VIBECART_CATALOG_URL, Core uses the fictional reference catalog for development. Configure a merchant catalog URL before treating products/prices as a real store catalog.

Without a Stripe secret, Checkout runs in clearly labeled demo mode. For live payments, configure STRIPE_SECRET_KEY in the hosting provider's secret/environment settings. Never commit secret values.

Useful public endpoints:

/start — merchant/client quickstart
/mcp — generic MCP transport/discovery
/api/cart — durable cart creation
/.well-known/ucp — UCP business discovery
/ucp/mcp — UCP-aware MCP transport
/mcp-clients.json — machine-readable client compatibility manifest
/llms.txt — concise machine-readable integration notes
/agents.md — agent-facing guide
/api/health — boolean readiness state without secret values
/cloud — managed Cloud offer

Security model

Merchant owns the Stripe account and receives merchant funds directly.
Trusted prices come from the configured server-side merchant catalog provider.
A configured remote merchant catalog fails closed rather than falling back to demo prices.
Client-supplied pricing is disabled by default and is prototype-only when explicitly enabled server-side.
Stripe webhook signatures are verified before post-payment processing.
Cart state is durable and versioned rather than trusted from the browser/agent.
Catalog, Stripe, database, and Cloud integration credentials remain server-side.
Public health/discovery endpoints expose readiness booleans/capabilities, not credential values.
Optional UCP capabilities are advertised only when their runtime dependencies are valid.

Protocol conformance

CI pins the released UCP v2026-04-08 source and executes VibeCart's real mappers through the official ucp-schema validator. Cart success/error payloads, catalog responses, discovery, and the private order mapper have release-pinned conformance gates.

Current reference limits

The remote catalog connector is intentionally a simple trusted JSON-provider contract, not yet a multi-merchant catalog control plane with merchant UI, inventory sync, or per-merchant credentials stored by VibeCart Cloud.
Inventory, automated tax calculation, shipping-rate calculation, returns/refunds, and a complete fulfillment lifecycle are not finished platform services.
Public UCP order lookup remains activation-gated until its Cloud/permalink runtime dependencies are configured.
Next.js App Router is the reference implementation; other frameworks should use adapters around the same Core protocol surface rather than fork commerce logic.

North star

VibeCart: commerce infrastructure for every AI agent. Build once. Sell everywhere AI can act.

License

MIT — free to use, modify, distribute, sublicense, and sell under the license terms.

VibeCart

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Online shops & paymentsi

Common questions

Alternatives

Spree Commerce: open-source B2B and marketplace ecommerce

Stripe MCP

MCP Cn Commerce

README from the maker

VibeCart

Live production surface

Generic MCP

Durable cart

UCP

Stripe checkout and orders

He Said Nothing physical-store pilot

Merchant catalog source

Optional when the feed is private:

Agent-client distribution

VibeCart Cloud

Quick start

Security model

Protocol conformance

Current reference limits

North star

License