mcp-registry/org.singchat/singchat · v0.1.0
As of 2026-10-27 09:03 UTC, the Singchat MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 8 minutes.
Free live chat and AI support agent. Auto-create a workspace and embed from your AI editor.
Point your MCP client at this streamable-http endpoint: https://mcp.singchat.org
17 of 17 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Forg.singchat%2Fsingchat/fixes
{
"name": "add_knowledge",
"description": "Train the AI agent by adding a knowledge source. type='url' crawls a website (up to 50 pages, fewer when the workspace knowledge-base quota is nearly full); type='qa' stores a single question/answer pair. Ingestion is asynchronous, the source starts as PENDING; poll `list_knowledge` for READY status.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"type"
],
"properties": {
"url": {
"type": "string",
"format": "uri",
"description": "Website root URL to crawl. Required when type='url'."
},
"type": {
"enum": [
"url",
"qa"
],
"type": "string",
"description": "'url' to crawl a website, or 'qa' to add a question/answer pair."
},
"answer": {
"type": "string",
"description": "The answer. Required when type='qa'."
},
"question": {
"type": "string",
"description": "The question. Required when type='qa'."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Add knowledge"
}{
"name": "fetch",
"description": "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 workspace; without a key it reads a SingChat help article. Returns id, title, text, url, and optional metadata.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "The document id returned by the search tool."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Fetch"
}{
"name": "get_analytics",
"description": "Return a compact analytics summary for this workspace over the last `days` days (default 30): conversation counts + resolution rate, message volume + AI share, plus a live snapshot of today (UTC).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"days": {
"type": "integer",
"default": 30,
"maximum": 365,
"minimum": 1,
"description": "Look-back window in days for the conversation/message stats (default 30)."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Get Analytics"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/org.singchat/singchat"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/org.singchat/singchat"}) over MCP.
configure_agent ~292 tokensmanage_faq ~276 tokensadd_knowledge ~239 tokensset_keywords ~232 tokenssingchat_setup ~220 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Forg.singchat%2Fsingchat?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Forg.singchat%2Fsingchat?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.singchat%2Fsingchat.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.singchat%2Fsingchat.svg :target: https://glimind.com/server/mcp-registry%2Forg.singchat%2Fsingchat?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:39e766c0f6eceafc…, first seen 2026-10-17, included at leaf 3409 of 78,426. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable other servers · most reliable retrieval servers · most reliable analytics servers · most reliable communication servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 09:03 UTC, the Singchat MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 8 minutes.
Singchat MCP server advertises 17 tools, including add_knowledge, claim_account, configure_agent, fetch, get_analytics.
Point your MCP client at this streamable-http endpoint: https://mcp.singchat.org
Glimind scanned all 17 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.