D
Warning
44/100
9 hours ago

VibeCart MCP Server

Enables AI agents to discover and interact with a merchant's commerce layer, including product listing and checkout creation, while payments settle directly to the merchant's Stripe account.

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

runjohnray2-lgtm

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
2 flows detected: VIBECART_CLOUD_INGEST_KEY. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Known vulnerabilities in dependencies: 12 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 6 credentials: STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, VIBECART_CART_ACCESS_SECRET, VIBECART_CATALOG_BEARER_TOKEN, VIBECART_CLOUD_INGEST_KEY, VIBECART_MERCHANT_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies12 high7 medium14 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highnext@15.3.9GHSA-267c-6grr-h53f

Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes

highnext@15.3.9GHSA-26hh-7cqf-hhc6

Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up

highnext@15.3.9GHSA-36qx-fr4f-26g5

Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n

highnext@15.3.9GHSA-89xv-2m56-2m9x

Next.js: Server-Side Request Forgery in Server Actions on custom servers

highnext@15.3.9GHSA-8h8q-6873-q5fj

Next.js Vulnerable to Denial of Service with Server Components

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretSTRIPE_SECRET_KEYWithout a Stripe secret, Checkout runs in clearly labeled demo mode. For live payments, configure in the hosting provider's secret/environment settings. Never commit secret values.
🔐 secretSTRIPE_WEBHOOK_SECRET
configVIBECART_ALLOW_UNTRUSTED_PRICING
🔐 secretVIBECART_CART_ACCESS_SECRET
🔐 secretVIBECART_CATALOG_BEARER_TOKENserver-side-secret
configVIBECART_CATALOG_URLWithout , Core uses the fictional reference catalog for development. Configure a merchant catalog URL before treating products/prices as a real store catalog.
🔐 secretVIBECART_CLOUD_INGEST_KEY
configVIBECART_CLOUD_INGEST_URL
configVIBECART_HOSTED_MODE
configVIBECART_MCP_ALLOWED_ORIGINS
🔐 secretVIBECART_MERCHANT_API_KEY
configVIBECART_MERCHANT_ID
configVIBECART_MERCHANT_NAME"Example Merchant"
configVIBECART_ORDER_PERMALINK_TEMPLATE
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployPOSTGRES_URL
// quality suggestions

Tool annotations

4/11 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

7/11 tools missing one or more hints — search_catalog (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); lookup_catalog (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_product (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

7/11 tools referenced in tests (64%)

Write tests that reference each tool by name so every tool has at least one test.

Secrets stay with their owner

2 secret/sensitive values flow into network calls (VIBECART_CLOUD_INGEST_KEY → dynamic, VIBECART_CLOUD_INGEST_KEY → dynamic)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Secrets not logged

2 secret values sent to console.log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 10 high severity in production deps — next@15.3.9 (high), next@15.3.9 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

2 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 7 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/runjohnray2-lgtm-vibecart-8b8p2k?variant=verified)](https://m8ven.ai/mcp/runjohnray2-lgtm-vibecart-8b8p2k)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 08301c1ae0a0e145f1fd854a90533e49a7451ad3
code hash: f011be4cb809880ddf8af321c688f6389e208afa8f0745209841d73e8167563b
verified: 8/19/2026, 9:18:22 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client