Home / MCP registry index / org.singchat/singchat
SingChat
org.singchat/singchat in the official MCP registry.
Endpoint https://mcp.singchat.org/.
The registry describes it as: Free live chat and AI support agent. Auto-create a workspace and embed from your AI editor.
We read its 17 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
ping singchat_setup get_embed_snippet claim_account list_conversations get_conversation reply_to_conversation resolve_conversation add_knowledge list_knowledge search_knowledge configure_agent set_keywords manage_faq get_analytics search fetch
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/org-singchat-singchat)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.