# org.singchat/singchat Free live chat and AI support agent. Auto-create a workspace and embed from your AI editor. - **Type:** MCP server - **Trust:** 60/100 (B), scored on the content rubric - **Verification:** community-indexed — nobody has claimed this listing - **Version:** 0.2.0 - **Author:** org.singchat - **License:** Unknown - **Endpoints:** streamable-http https://mcp.singchat.org - **Source:** https://mcp.singchat.org - **Endpoint health:** reachable (last checked 2026-09-13T12:17:21.188Z, 4 samples) — uptime is not a security property and is not part of the trust score - **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport) ## Trust 60/100 (B), scored on the content rubric - Publisher verified: no - Install scripts: nothing suspicious found - Prompt-injection scan: clean - Obfuscation scan: clean - Evidence age: 1 day ## Security scan - **Status:** clean - **Scanned:** 2026-09-13T12:17:21.188Z - **Version scanned:** live - **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it. **Findings** - injection-shaped content (note) in the `configure_agent` tool: References the system prompt ## Tools 17 declared. Observed from a live `tools/list` probe. - `ping` — Health check for the SingChat MCP server. Returns 'pong' and whether this request is authenticated to a workspace. - `singchat_setup` — Get the user up and running with SingChat live-chat. Call this FIRST. If no authenticated workspace is configured, this creates a brand-new free workspace and r - `get_embed_snippet` — Return the SingChat chat-widget embed code for this workspace's web inbox, in three flavors: plain HTML, React (useEffect), and Next.js (next/script). Requires - `claim_account` — Return the link to claim (permanently secure) this SingChat workspace by setting an email and password. Use this for workspaces that were auto-created via MCP s - `list_conversations` — List the workspace's support conversations (agent/inbox view), newest activity first. Optionally filter by status or a free-text search over the contact name/em - `get_conversation` — Fetch a single conversation with its contact details and the most recent messages (oldest→newest). - `reply_to_conversation` — Send an agent reply through a supported SingChat real-time inbox. This takes the conversation over from the AI and broadcasts the message to the visitor and age - `resolve_conversation` — Mark a conversation as RESOLVED (closes it). The visitor's widget will no longer show it as active. - `add_knowledge` — Train the AI agent by adding a knowledge source. type='url' crawls a website (up to 50 pages); type='qa' stores a single question/answer pair. Ingestion is asyn - `list_knowledge` — List all knowledge documents for this workspace with their processing status (PENDING | PROCESSING | READY | FAILED) and chunk counts. Use this to check whether - `search_knowledge` — Semantic search over the workspace knowledge base. Returns the most relevant chunks (with source document title and similarity score) for a query. Only searches - `configure_agent` — Configure this workspace's AI support agent. All fields are optional, only the fields you pass are updated; the rest keep their current values. Call with no fie - `set_keywords` — Add a keyword auto-reply rule: when an inbound message matches any of the keywords, the bot replies with the given text. Good for canned FAQ-style triggers (e.g - `manage_faq` — List, create, update, or delete this workspace's FAQ items (shown in the chat widget and usable by the AI agent). Set `action` to 'list' | 'create' | 'update' | - `get_analytics` — Return a compact analytics summary for this workspace over the last `days` days (default 30): conversation counts + resolution rate, message volume + AI share, - `search` — Search SingChat for relevant documents. When called with a workspace API key, this searches that workspace knowledge base; without a key it searches SingChat's - `fetch` — Fetch the full text of a single document by id, using an id returned by the search tool. With a workspace API key this reads a knowledge document from that work ## Install **Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it. **Cautions** (coverage gaps and advisories — never blocking) - No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it. - No publisher has proved control of this listing; it is indexed, not vouched for. **Config** (claude-code): ```json "{\n \"mcpServers\": {\n \"singchat\": {\n \"type\": \"http\",\n \"url\": \"https://mcp.singchat.org\"\n }\n }\n}" ``` ## Blast radius Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface. - Floor 9, ceiling 27 (tier: unknown) - `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low. - This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score. ## Machine-readable views of this entry - Signed JSON: https://forgeregistry.com/api/v1/packages/org.singchat%2Fsingchat - Install plan: https://forgeregistry.com/api/v1/packages/org.singchat%2Fsingchat/install-plan - Alternatives: https://forgeregistry.com/api/v1/alternatives/org.singchat%2Fsingchat - HTML page: https://forgeregistry.com/registry/org.singchat%2Fsingchat - MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan` ## About this document Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.