T
toby7979/sealmyapp-tools
Free MCP server, Cursor rule and Claude skill that help AI coding assistants avoid common security holes in vibe-coded apps (Supabase RLS, leaked keys). By SealMyApp.
无 SECURITY.md
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
- 复制上面的命令
- 粘成
claude_desktop_config.json里mcpServers的一项(本地服务器用 command + args,示例见 客户端接法) - 重启客户端
客户端配置(取自该仓库的安装命令)
{
"mcpServers": {
"toby7979-sealmyapp-tools": {
"command": "npx",
"args": ["-y", "github:toby7979/sealmyapp-tools"]
}
}
}解析自我们于 2026-10-26 抓取的该仓库 README;我们未执行过。
command/args 来自仓库写明的安装命令;不确定时请以该项目 README 为准。
VS Code(.vscode/mcp.json —— 键名是 servers)
{
"servers": {
"toby7979-sealmyapp-tools": {
"command": "npx",
"args": ["-y", "github:toby7979/sealmyapp-tools"]
}
}
}VS Code 顶层键是 <code>servers</code>,其余与上面那份相同。
Claude Code(命令行)
claude mcp add --transport stdio toby7979-sealmyapp-tools -- npx -y github:toby7979/sealmyapp-tools
Claude Code 不收 JSON 文件,用这条命令直接加。
配置项的键名以你的客户端为准:客户端与 CLI
- ★ 数取值
- 0 ★ · toby7979/sealmyapp-tools · 取自 GitHub 搜索 API · (2026-11-13 20:00:50 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-10-23 · 最近见到 2026-11-14 · 共见到 26 次 · 被 23 个来源列出
- 评分构成
- 综合分 2,300 · 23 个来源 · mcp
- 安装
npx -y github:toby7979/sealmyapp-tools
常见问题(答案都来自我们的记录)
怎么安装?
该仓库给出的安装命令是
npx -y github:toby7979/sealmyapp-tools。我们的记录里它是仓库自己提供的;不保证在你的客户端上直接可用。它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
toby7979/sealmyapp-tools;我们收录于 2026-10-23;最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# SealMyApp tools
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
Free, open-source security helpers for vibe-coded apps (Lovable, Bolt, Cursor, Replit, v0, and anything on Supabase or Firebase):
An MCP server your AI assistant can call to check whether a key is safe to expose, audit Supabase Row Level Security, generate safe RLS policies and run a pre-launch checklist.
A Cursor rule, an Agent Skill (Claude Code and other skill-aware agents) and an AGENTS.md snippet that stop the AI from leaking secrets or "fixing" empty results with using (true).
Everything here runs locally and makes no network calls.
> Made by SealMyApp, a paid service that finds, fixes and monitors security holes in vibe-coded apps. The tools in this repo are free and MIT-licensed, and you don't need a SealMyApp account to use them.
## Guides
Railway breach (21 Oct 2026): how to rotate your secrets, in order
## Install the MCP server
Requires Node.js 20+ and git. The first run downloads and builds the package from GitHub, so it takes a little longer.
Claude Code
bash
claude mcp add sealmyapp -- npx -y github:toby7979/sealmyapp-tools
Claude Desktop (claudedesktopconfig.json: Settings → Developer → Edit Config)
json
"mcpServers": {
"sealmyapp": {
"command": "npx",
"args": ["-y", "github:toby7979/sealmyapp-tools"]
Cursor (.cursor/mcp.json in your project, or ~/.cursor/mcp.json for all projects)
json
"mcpServers": {
"sealmyapp": {
"command": "npx",
"args": ["-y", "github:toby7979/sealmyapp-tools"]
VS Code (.vscode/mcp.json; note the top-level key is servers)
json
"servers": {
"sealmyapp": {
"type": "stdio",
"command": "npx",
"args": ["-y", "github:toby7979/sealmyapp-tools"]
Then ask your assistant things like "Is a key starting sklive safe in my frontend?", "Give me SQL to audit RLS in my Supabase project" or "Run the pre-launch security checklist for my Lovable app".
## Tools
| Tool | Input | What it returns |
| checkkeyexposure | keyorprefix | Whether the key is public by design (Supabase anon/publishable, Stripe pk, Firebase web key) or secret (sklive, servicerole, sk-ant-, ...), and what to do next: rotate first if it's secret. Classified offline from the format. Pass only a prefix; the full key is never echoed back. |
| supabaserlsauditsql | none | Read-only SQL that lists tables without RLS, policies whose USING/WITH CHECK is true, views that bypass RLS and public buckets, plus how to read the results. |
| rlspolicytemplate | tablekind: profiles \| posts \| orders \| messages \| files; optional ownercolumn | Example owner-based policies (select/insert/update/delete with auth.uid()) and caveats. |
| vibesecuritychecklist | optional builder: lovable \| bolt \| cursor \| replit \| v0 \| other | A pre-launch checklist covering secrets, Supabase, Firebase, auth and payments, with notes for your builder. |
| scanmyappinstructions | url | How to run a free, ownership-verified scan of an app you own at sealmyapp.com, and a link to start it. It does not call any API or start a scan. |
Every tool's output ends with a one-line link to SealMyApp's free scan.
## Cursor rule
Copy rules/cursor/vibe-security.mdc into your project's .cursor/rules/ folder:
bash
An MCP server your AI assistant can call to check whether a key is safe to expose, audit Supabase Row Level Security, generate safe RLS policies and run a pre-launch checklist.
A Cursor rule, an Agent Skill (Claude Code and other skill-aware agents) and an AGENTS.md snippet that stop the AI from leaking secrets or "fixing" empty results with using (true).
Everything here runs locally and makes no network calls.
> Made by SealMyApp, a paid service that finds, fixes and monitors security holes in vibe-coded apps. The tools in this repo are free and MIT-licensed, and you don't need a SealMyApp account to use them.
## Guides
Railway breach (21 Oct 2026): how to rotate your secrets, in order
## Install the MCP server
Requires Node.js 20+ and git. The first run downloads and builds the package from GitHub, so it takes a little longer.
Claude Code
bash
claude mcp add sealmyapp -- npx -y github:toby7979/sealmyapp-tools
Claude Desktop (claudedesktopconfig.json: Settings → Developer → Edit Config)
json
"mcpServers": {
"sealmyapp": {
"command": "npx",
"args": ["-y", "github:toby7979/sealmyapp-tools"]
Cursor (.cursor/mcp.json in your project, or ~/.cursor/mcp.json for all projects)
json
"mcpServers": {
"sealmyapp": {
"command": "npx",
"args": ["-y", "github:toby7979/sealmyapp-tools"]
VS Code (.vscode/mcp.json; note the top-level key is servers)
json
"servers": {
"sealmyapp": {
"type": "stdio",
"command": "npx",
"args": ["-y", "github:toby7979/sealmyapp-tools"]
Then ask your assistant things like "Is a key starting sklive safe in my frontend?", "Give me SQL to audit RLS in my Supabase project" or "Run the pre-launch security checklist for my Lovable app".
## Tools
| Tool | Input | What it returns |
| checkkeyexposure | keyorprefix | Whether the key is public by design (Supabase anon/publishable, Stripe pk, Firebase web key) or secret (sklive, servicerole, sk-ant-, ...), and what to do next: rotate first if it's secret. Classified offline from the format. Pass only a prefix; the full key is never echoed back. |
| supabaserlsauditsql | none | Read-only SQL that lists tables without RLS, policies whose USING/WITH CHECK is true, views that bypass RLS and public buckets, plus how to read the results. |
| rlspolicytemplate | tablekind: profiles \| posts \| orders \| messages \| files; optional ownercolumn | Example owner-based policies (select/insert/update/delete with auth.uid()) and caveats. |
| vibesecuritychecklist | optional builder: lovable \| bolt \| cursor \| replit \| v0 \| other | A pre-launch checklist covering secrets, Supabase, Firebase, auth and payments, with notes for your builder. |
| scanmyappinstructions | url | How to run a free, ownership-verified scan of an app you own at sealmyapp.com, and a link to start it. It does not call any API or start a scan. |
Every tool's output ends with a one-line link to SealMyApp's free scan.
## Cursor rule
Copy rules/cursor/vibe-security.mdc into your project's .cursor/rules/ folder:
bash
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/toby7979-sealmyapp-tools/)
- 来源
- awesome · https://github.com/toby7979/sealmyapp-tools
- 按领域浏览
- MCP 服务
- 收录来源
- 23 个独立来源
- 收录于
- 今天
- 安全策略
- 我们没在该仓库根目录找到
SECURITY.md(这不代表不安全)
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。