# Insecure MCP Demo ## Overview This project demonstrates a vulnerable MCP server and multiple clients, including a proof-of-concept attack client
Most database access work still happens through a UI a human drives. Insecure MCP Demo MCP server moves it into the conversation instead. # Insecure MCP Demo ## Overview This project demonstrates a vulnerable MCP server and multiple clients, including a proof-of-concept attack client and also a good client. It is designed for educational purposes to showcase potential.
python cursor.execute("INSERT INTO records (name, address) VALUES (?, ?)", (name, address)) 2. Restrict Dangerous Tools: - Remove or strictly limit tools like execute_sql and get_env_variable. - Only expose necessary functionality. 3. Implement Authentication & Authorization: - Require users to authenticate and check permissions before allowing access to sensitive tools or data. 4. Validate and Sanitize Input: - Check and sanitizeThe server publishes 1 tool. What each one is for:
Vulnerability — ** Prone to SQL injection due to direct string interpolation of user input into SQL queriesSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Insecure MCP Demo's toolset — Vulnerability — is a fair guide to whether it matches your workflow. It is maintained by kenhuangus; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Insecure MCP Demo's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Vulnerability | ** Prone to SQL injection due to direct string interpolation of user input into SQL queries. |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.