Stripe MCP
MCP server integrating with Stripe - tools for customers, products, payments, and more.
Check Supabase migrations for RLS and grant gaps; fixes for Supabase, Vercel, Stripe errors.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 22/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 42/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 VibeRaven。按照 https://mcp.popnx.com/i/ohad6k-viberaven-guides.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(viberaven.dev) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
VibeRavenhttps://viberaven.dev/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsVibeRaven
用 VibeRaven 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 VibeRaven,或回答中出现 VibeRaven 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
VibeRavenhttps://viberaven.dev/mcp开启新聊天,输入前先从插件列表中选择 VibeRaven
用 VibeRaven 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 VibeRaven,或回答中出现 VibeRaven 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user viberaven-guides https://viberaven.dev/mcp应能看到 VibeRaven 在列表中并显示已连接
用 VibeRaven 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 VibeRaven,或回答中出现 VibeRaven 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 VibeRaven 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 VibeRaven,或回答中出现 VibeRaven 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 VibeRaven 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 VibeRaven,或回答中出现 VibeRaven 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://viberaven.dev/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user viberaven-guides https://viberaven.dev/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"viberaven-guides": {
"url": "https://viberaven.dev/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"viberaven-guides": {
"type": "http",
"url": "https://viberaven.dev/mcp"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
工具名称和描述与服务器在 2026年11月18日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
race_two_usersrace_two_users({"sql":"CREATE TABLE public.quota(id int PRIMARY KEY, remaining int); INSERT INTO public.quota VALUES (1,1);","spec":{"rule":"Quota cannot go below zero","actors":[{"id":"A","role":"postgres","steps":["UPDATE public.quota SET remaining=remaining-1 WHERE id=1 AND re
check_supabase_migrationscheck_supabase_migrations({"sql":"create table public.notes (id bigint);"}) Use when reviewing Supabase migration changes for missing RLS or policies, unrestricted read/write policies, exposed security definer functions and Data API grant gaps. Pass file contents: sql contains on
check_github_repocheck_github_repo({"repo":"owner/name"}) Check the Supabase migrations of a public GitHub repository for missing RLS or policies, policies that let anyone read or write every row, exposed security definer functions and Data API grant gaps. Use it when the user names or links thei
provider_playbookprovider_playbook({"provider":"supabase","topic":"grants"}) Use before implementing a feature that touches a provider, when setup or integration rules are needed. Returns versioned setup guidance, gotchas, dated changes, integration seams, existing repo checks and planned live ch
recent_provider_changesrecent_provider_changes({"provider":"supabase","query":"42501","limit":5}) Use when a provider update may explain changed behavior, or a deployment needs review against dated provider changes. Returns candidate changes, documented errors or symptoms, fixes, date meanings and offi
explain_findingexplain_finding({"gap_id":"rls_disabled"}) Use after a check returns a finding id, such as rls_disabled or env_var_drift, to understand and fix that VibeRaven 1.10.0 finding. Returns detection scope, impact, fix guidance and coverage limits quoted from viberaven.dev with source l
search_guidessearch_guides({"query":"supabase tables missing rls"}) Find troubleshooting steps for exact errors in Supabase RLS, Realtime and auth; Clerk middleware and sessions; Better Auth origins and OAuth callbacks; Vercel environment variables and deployments; Stripe webhooks; or Storybo
launch_checklistlaunch_checklist({"stack":"nextjs-supabase-vercel"}) Use for a broad pre-launch review of a Lovable + Supabase app or a Next.js + Supabase app on Vercel. For a specific failing request, use search_guides. Returns a published manual checklist with sources and an optional local rep
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月18日
注册名称已通过 GitHub 账户 ohad6k 验证,该账户拥有此仓库
代码最后更新于昨天
使用 MIT
在 3898 毫秒内响应(HTTP 200)
无需登录
已读取 8 个工具描述,未发现针对 AI 的隐藏指令
云端地址最近 4 次检查中有 4 次响应 · 最近一次 3,898 ms · 检查于 2026年11月18日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/ohad6k-viberaven-guides)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于昨天,最新版本(1.1.0)于21天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:Stripe MCP, flightclaw, Trade It, Marketplace Ad Pros: Amazon Ads & Seller Central, idealo MCP Server
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP server integrating with Stripe - tools for customers, products, payments, and more.
Search ~300 airlines and book flights with a checkout link. OAuth sign-in by email code.
Connect brokerage accounts to AI assistants: holdings, orders, asset lookup, and approved trading.
Amazon Ads, Seller Central, Vendor Central and AMC data for AI agents. Read-only by default.
Search products, compare prices and discover deals across 6 European markets with your AI assistant.
| 本项 VibeRaven | Stripe MCP | flightclaw | Trade It | Marketplace Ad Pros: Amazon Ads & Seller Central | idealo MCP Server | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | MIT | MIT | CC0-1.0 | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
VibeRaven VibeRaven checks AI-built apps on Vercel + Supabase for launch gaps before you ship: tables without RLS, permissive policies such as using (true) , service_role keys in client code, anon-callable security definer functions, the wrong pooler port and unverified Stripe webhooks. Run npx -y viberaven@1.7.6 check in your app's folder. It reads the repository on your machine, needs no account, and names the file and line for each gap.
Website · What it checks · When to use it · How it compares · Local Studio · Agent skills · Releases
Requires Node.js 20 or newer. From your app's project root:
npx -y viberaven@1.7.6 check
npx -y viberaven@1.7.6 checknpx -y viberaven@1.7.6 checknpx.cmd if npx is blocked by the execution policy.It reads supabase/migrations, your client and server code, package.json and .env.example. It does not connect to your Supabase project or send requests to your app. It exits 1 when it finds a blocker, so it also works as a CI step.
| Finding | Gap ID | Related Supabase Security Advisor lint |
|---|---|---|
| A public table created in a migration with row level security never enabled | rls_disabled | rls_disabled_in_public (guide) |
A policy with using (true) that lets anyone read or write every row | rls_policy_allows_all_write, rls_policy_allows_all_read | none |
The service_role key in a file that ships to the browser, or under a NEXT_PUBLIC_ name | service_role_key_in_client_code, service_role_key_in_client_env | none |
A security definer function in public that no migration closes to anon | security_definer_function_executable | anon_security_definer_function_executable (guide) |
| A direct Postgres connection on port 5432 from serverless code, instead of the transaction pooler on 6543 | pooler_port_mismatch | none |
| A Stripe webhook handler that never checks the signature over the raw body | unverified_stripe_webhook | none |
Env vars that code reads but .env.example does not list, queries with no row limit, no error monitoring | env_var_drift, unbounded_query, missing_monitoring | none |
Two other Security Advisor lints come up often in the same apps. VibeRaven has no rule for them yet, and the guides explain the fix:
security_definer_view: what it means and how to fix itfunction_search_path_mutable: what it means and how to fix itFor a before-and-after run on one migration, see the missing-RLS example.
Historical output from viberaven check 1.7.2 on a synthetic Next.js + Supabase app with one of each gap (project path shortened):
viberaven check · ~/my-app
🔴 No RLS policy proof in migrations (rls_disabled) 1 public table without row level security: public.profiles (supabase/migrations/20260301000000_init.sql:1). The Data API does not enforce row restrictions for roles and operations allowed by the table's grants. Verify those grants to determine who can read or change rows. 🔴 A policy lets anyone write every row (rls_policy_allows_all_write) Policy "orders are editable" on public.orders (supabase/migrations/20260301000000_init.sql:13) lets anyone, signed in or not, update every row, to any values: using (true). 🔴 Service role key used in client code (service_role_key_in_client_code) app/admin/page.tsx:4: reads NEXT_PUBLIC_SUPABASE_SERVICE_ROLE_KEY. NEXT_PUBLIC_* variables are exposed to client code by Next.js, and the service role key skips RLS entirely. Move the call behind a server route or edge function and rotate the key. 🟡 Security definer function callable by the Data API roles (security_definer_function_executable) public.grant_credits(uuid, integer) at supabase/migrations/20260301000000_init.sql:15 is security definer, so it runs with its owner's rights and RLS does not limit what it touches. No migration revokes EXECUTE from public, anon, authenticated, so anyone holding the anon key can call it at /rest/v1/rpc/grant_credits. If only the server calls it, add: revoke execute on function public.grant_credits(uuid, integer) from public, anon, authenticated; Fix: revoke execute on function public.grant_credits(uuid, integer) from public, anon, authenticated; 🟡 Stripe webhook does not verify the signature (unverified_stripe_webhook) 1 Stripe webhook handler without signature verification over the raw body: app/api/stripe/webhook/route.ts (no signature check (constructEvent), no stripe-signature header, no raw body). Anyone who finds the URL can post a fake event, for example a paid checkout. 🟡 Env vars used in code but missing from .env.example (env_var_drift) Code reads 1 environment variable that .env.example does not document (NEXT_PUBLIC_SUPABASE_SERVICE_ROLE_KEY). Fresh clones, CI, and the production deploy can silently run without them. 🟡 Database queries with no row limit (unbounded_query) 1 file run Supabase selects or Prisma findMany with no .limit()/.range()/take bound (app\admin\page.tsx). These work with 50 test rows and melt with 50,000 production rows. ⚪ No error monitoring detected (missing_monitoring) No Sentry/PostHog (or similar) instrumentation was found. Production errors will only surface when users complain.
Verdict: ❌ 3 blockers, 4 warnings · score 5 Fix: viberaven fix · Details: ~/my-app\.viberaven\agent-tasklist.md Optional live catalog: npx -y viberaven@1.7.6 live start --provider supabase --project --json (read-only metadata; account required; server availability not checked; user approves in the browser and approves the project read). Keep checks running with your agent: npx -y viberaven@1.7.6 init
Every result also lands in .viberaven/ as markdown and JSON (agent-tasklist.md, gate-result.json, context-map.json), so a coding agent and your git history can read it.
Use it:
It is not the right tool when:
These tools answer different questions, and most launches need more than one of them.
| Tool | What it checks | Where it runs | How it fits with VibeRaven |
|---|---|---|---|
| Supabase Security Advisor | Lints on the live database: RLS disabled, security definer views and functions, mutable search_path and more | Supabase dashboard, against the deployed project | Advisor sees what is live. VibeRaven reads the migrations before they are applied, plus the client code and env files the database never sees. |
| OWASP ZAP | Dynamic scan of a running web app over HTTP: injection, XSS, headers, cookies | Against a deployed or local URL | ZAP tests the app from outside. VibeRaven reads the repo and knows Supabase grants, policies and keys. |
| Semgrep, Snyk, CodeQL | General static analysis and dependency vulnerabilities across many languages | CI or locally, on source code | Broad code rules and CVEs. VibeRaven is narrow: Supabase RLS and grants, service_role exposure, the pooler port and Stripe webhooks. |
| Playwright | End-to-end tests you write, driving a real browser | Locally or in CI, against a running app | Playwright proves the flows you test. A test that signs in as user A and tries to read user B's rows is the live check that VibeRaven's RLS findings point to. |
We ran the check on the Supabase migrations of 512 public Lovable repos. From the write-up:
In a static read of 512 public Lovable projects on GitHub with a supabase/migrations folder (October 2026), 47.3% (242) define at least one security definer function in the public schema that a signed-out caller with the anon key can run at /rest/v1/rpc.
The post has the method, the limits and the fix. An earlier post covers RLS policies in the same 512 apps.
npx -y viberaven@1.7.6 fix # list gaps with safe automatic recipes
npx -y viberaven@1.7.6 fix --gap --dry-run # preview one recipe npx -y viberaven@1.7.6 fix --gap # apply it npx -y viberaven@1.7.6 audit --vercel-supabase # RLS in migrations, pooler port, service_role key npx -y viberaven@1.7.6 --strict # the verdict as an exit code for CI (exit 1 on not_clear; warnings exit 0)
The rls_disabled recipe adds a mig