IKANGAI Vibe Support
Server Details
Safety notices and real examples for people who build apps with AI coding tools. Free, no key.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 6 tools
The list_* tools each target a clearly distinct resource (notices, showcase, toolbox, tool updates), and get_notice is separated by being an id-based detail fetch. The main soft spot is search, which spans all three content types and is also recommended as a 'use first' entry point, so an agent must decide between searching and browsing; get_notice also doubles as the detail view for showcase entries, which slightly blurs its stated notice focus.
Five of six tools follow a clean verb_noun pattern (get_notice, list_notices, list_showcase, list_toolbox, list_tool_updates). The lone 'search' breaks the pattern as a bare verb, a minor but noticeable deviation in an otherwise predictable set.
Six tools is well-scoped for a guidance/reference server: one detail fetcher, four listing endpoints for distinct content types, and one cross-cutting search. No tool appears redundant or padded, and nothing essential is obviously absent at this size.
The surface covers the full read lifecycle for each content type: list plus detail for notices and showcase, listings for toolbox and update sources, and search across everything. Minor gaps remain — toolbox entries have no id-based detail fetch (only summaries via list_toolbox), and update sources can only be listed, not queried individually — but agents can work around these through search and the listing output.
Available Tools
6 toolsget_noticeRead one notice or showcase entry in fullARead-onlyInspect
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.
Inputs: id (required).
list_noticesList safety noticesARead-onlyInspect
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.
Inputs: tool.
list_showcaseWhat people have built with AIARead-onlyInspect
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.
Inputs: tool.
list_toolboxReady-made tools and add-onsBRead-onlyInspect
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.
Inputs: no named parameters.
list_tool_updatesWhere tools post updatesARead-onlyInspect
Where each AI building tool announces changes and security fixes, and whether it keeps a dated list of security fixes.
Inputs: tool.
searchSearch Vibe SupportARead-onlyInspect
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.
Inputs: query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Production-safety audits for AI-generated code, with a fix for every finding.
Free security scan for AI-written GitHub repos: leaked keys, .env, eval, SQLi, CORS.
Checks AI-written code for leaked keys and made-up packages, on your machine. Never uploads code.
Free passive security scan for AI-built apps: leaked API keys, public .env files, security headers
Related MCP Servers
- AlicenseAqualityBmaintenanceA free, read-only server that lets users diagnose production AI-agent risks: it flags over-privileged API keys from permission descriptions, scans code snippets for the signals that prevent duplicate execution, and explains guard patterns such as idempotency keys, approval gates, outboxes, and circuit breakers. It makes no network calls or writes, and rejects inputs that look like real secrets.328 PyPIMIT
- AlicenseAqualityDmaintenanceCodeSafer is an MCP server that scans AI-generated code for 9 categories of hidden security threats — including invisible Unicode, Trojan Source, homoglyphs, and rules file backdoors — using static analysis plus CodeBERT deep learning. Runs locally, free tier available.688 npm1MIT
- AlicenseAqualityDmaintenanceCognitive security for AI-assisted development, preventing dangerous commands and large AI code rewrites when fatigued.454 npmMIT
- AlicenseAqualityBmaintenanceLocal security layer for coding agents: keeps secret values out of what Claude Code, Codex CLI, Cursor and OpenCode send to their model, and checks untrusted text for prompt injection. MIT, runs on your machine, no account.45MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.