Safety notices and real examples for people who build apps with AI coding tools. Free, no key.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
One notice or showcase entry as Markdown: whether it applies, the problem, what could happen, the steps with the messages to paste, and every source it is based on.
The id from search, list_notices or list_showcase.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http vibe-support https://vibe.ikangai.com/mcp
One notice or showcase entry as Markdown: whether it applies, the problem, what could happen, the steps with the messages to paste, and every source it is based on.
| Argument | Type | Description |
|---|---|---|
| id* | string | The id from search, list_notices or list_showcase. |
{
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "The id from search, list_notices or list_showcase."
}
},
"additionalProperties": false
}List the safety and upkeep notices: title, topic, who each one is for, a summary and its id. Pass the tool the person builds with to get only what applies to it. Use this before work on login, payments, personal data or deleting data, and when asked what to check before going live. Call get_notice with an id for the checklist, the steps and the messages to paste.
| Argument | Type | Description |
|---|---|---|
| tool | string | Only what applies to this tool. Leave out for everything. |
{
"type": "object",
"properties": {
"tool": {
"enum": [
"lovable",
"bolt",
"cursor",
"claude",
"gemini",
"devin",
"supabase",
"vercel"
],
"type": "string",
"description": "Only what applies to this tool. Leave out for everything."
}
},
"additionalProperties": false
}Real games, rebuilt apps and tools that people made mainly with AI coding tools: who built it and with what, and a summary. Use it when the person wants ideas, asks what is possible, or doubts they can build something. Each entry rests on the builder's own account and another source; the projects are not tested by us. Call get_notice with an id for how it was built and what was hard.
| Argument | Type | Description |
|---|---|---|
| tool | string | Only what applies to this tool. Leave out for everything. |
{
"type": "object",
"properties": {
"tool": {
"enum": [
"lovable",
"bolt",
"cursor",
"claude",
"gemini",
"devin",
"supabase",
"vercel"
],
"type": "string",
"description": "Only what applies to this tool. Leave out for everything."
}
},
"additionalProperties": false
}Where each AI building tool announces changes and security fixes, and whether it keeps a dated list of security fixes.
| Argument | Type | Description |
|---|---|---|
| tool | string | Only what applies to this tool. Leave out for everything. |
{
"type": "object",
"properties": {
"tool": {
"enum": [
"lovable",
"bolt",
"cursor",
"claude",
"gemini",
"devin",
"supabase",
"vercel"
],
"type": "string",
"description": "Only what applies to this tool. Leave out for everything."
}
},
"additionalProperties": false
}Tools that already exist, add-ons for AI coding tools, safety tools, and popular tools to be careful with. Each has a plain description, its licence, when it was last updated and any caution. Being listed is not a safety check.
No arguments.
{
"type": "object",
"properties": {},
"additionalProperties": false
}Find notices, showcase entries and Toolbox tools by a few words, for example 'stripe refund', 'delete user data', 'supabase access rules' or 'multiplayer game'. Use this first when you know what the person is about to do. Returns the best matches with their ids; call get_notice for one in full.
| Argument | Type | Description |
|---|---|---|
| query* | string | A few plain words. |
{
"type": "object",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"description": "A few plain words."
}
},
"additionalProperties": false
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 21, 2026.