Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

VibeCart

REMOTE · VIBECART.VERCEL.APP

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

0 this week 88 Trust /100

Last scanned (20 hours ago)

Scores higher than 96% of remote servers

Reachable. Last reached 4 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 305 tokens (~76/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 17 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 19 Aug 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “vibecart.create_checkout” rewrote its description, which is the text the model reads security
    • Tool “vibecart.get_product” rewrote its description, which is the text the model reads security
    • Tool “vibecart.list_products” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • Schema quality: excellent → good functional
  • 18 Aug 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://vibecart.vercel.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.vercel.app CN=WR1,O=Google Trust Services,C=US 31 Oct 2026 29 Jan 2027 RSA 2048 SHA256-RSA 9c5f0e6a35c955e113044c86848e4cd5
SANs: *.vercel.app
CN=WR1,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7fd9e2c2d2048a0474b627a26d0868a7
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of vibecart.vercel.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
vercel.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://vibecart.vercel.app/mcp Verified 200
http (plaintext) http://vibecart.vercel.app/mcp HTTPS enforced 308 https://vibecart.vercel.app/mcp
MCP tools · 4 exposed · ~243 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
vibecart.create_checkout ~117

Creates a hosted checkout URL for one or more trusted merchant-catalog products. Legacy productId + quantity input remains supported; new integrations should use items[]. VibeCart resolves all prices server-side. This can contact Stripe but never charges by itself; the customer must complete Stripe Checkout.

NameTypeReqDescription
itemsarray–Trusted product IDs and quantities for a multi-item checkout.
productIdstring–Legacy single-product input. Use either productId or items, not both.
quantityinteger–Legacy single-product quantity.
NameTypeReqDescription
checkoutUrlstring|null––
codestring––
detailsobject––
errorstring––
itemsarray––
messagestring––
modestring––
productIdstring––
quantityinteger––
successbooleanyes–
totalCentsinteger––
untrustedPricingboolean––

No examples provided.

vibecart.get_integration_instructions ~41

Returns concise Next.js App Router guidance for installing VibeCart with trusted catalog pricing, multi-item checkout, and the shared MCP endpoint.

Input schema present but exposes no named parameters.

NameTypeReqDescription
checkoutRoutestringyes–
componentstringyes–
frameworkstringyes–
machineReadableSpecstringyes–
mcpEndpointstringyes–
rulesarrayyes–
successbooleanyes–

No examples provided.

vibecart.get_product ~54

Looks up one product and its trusted USD-cent price from the configured merchant catalog. Does not access Stripe or create a checkout.

NameTypeReqDescription
productIdstringyesA stable ID returned by vibecart.list_products.
NameTypeReqDescription
codestring––
errorstring––
productobject––
successbooleanyes–

No examples provided.

vibecart.list_products ~31

Lists products from the configured trusted merchant catalog. Use the returned stable IDs for product lookup or checkout.

Input schema present but exposes no named parameters.

NameTypeReqDescription
productsarrayyes–
successbooleanyes–

No examples provided.

Install

How do I install the VibeCart MCP server?

VibeCart is a hosted endpoint at https://vibecart.vercel.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · vibecart.vercel.app

# add to Claude Code
claude mcp add --transport http runjohnray2-lgtm-vibecart 'https://vibecart.vercel.app/mcp'
Common questions

What is the VibeCart MCP server?

VibeCart is an MCP server listed in the public MCP registry as io.github.runjohnray2-lgtm/vibecart. Agent-native commerce with trusted catalog, durable carts, and Stripe Checkout via MCP and UCP. This page covers its hosted endpoint (https://vibecart.vercel.app/mcp).

Is the VibeCart MCP server safe to use?

VibeCart scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the VibeCart MCP server expose?

VibeCart exposes 4 tools: vibecart.list_products, vibecart.get_product, vibecart.get_integration_instructions, vibecart.create_checkout. Their descriptions and schemas cost roughly 243 tokens of context every time the server is loaded.

Does the VibeCart MCP server require authentication?

No. We connected to VibeCart without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the VibeCart MCP server still maintained?

VibeCart is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.