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.
no SECURITY.md
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
- Copy the command above
- Paste it as one entry under
mcpServersinclaude_desktop_config.json— local servers take command + args (example: clients) - Restart your client
Client config (built from the install command this repo gives)
{
"mcpServers": {
"toby7979-sealmyapp-tools": {
"command": "npx",
"args": ["-y", "github:toby7979/sealmyapp-tools"]
}
}
}Parsed from the README we fetched on 2026-10-26; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"toby7979-sealmyapp-tools": {
"command": "npx",
"args": ["-y", "github:toby7979/sealmyapp-tools"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio toby7979-sealmyapp-tools -- npx -y github:toby7979/sealmyapp-tools
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 0 ★ · toby7979/sealmyapp-tools · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-23 · last seen 2026-11-14 · seen 26× · listed by 23 sources
- Score
- score 2,300 · 23 sources · mcp
- Install
npx -y github:toby7979/sealmyapp-tools
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx -y github:toby7979/sealmyapp-tools. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
toby7979/sealmyapp-tools;first catalogued 2026-10-23;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# 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
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/toby7979-sealmyapp-tools/)
- Source
- awesome · https://github.com/toby7979/sealmyapp-tools
- Browse by field
- MCP servers
- Listed by
- 23 independent sources
- added
- today
- Security policy
- no
SECURITY.mdat the repository root (which does not mean it is unsafe)
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.