_ registry / mcp streamable-http · checked 2h ago

singchat

https://mcp.singchat.org

Registry code: bd1327aae9b8354d

api record

Free live chat and AI support agent. Auto-create a workspace and embed from your AI editor.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.singchat.org
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is singchat live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is singchat free to use?
No — it asks for a key or a login before it will serve.
What tools does singchat have?
17 tools: fetch, search, search_knowledge, get_conversation, get_analytics, list_conversations, singchat_setup, claim_account, ….
Is singchat safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
634ms

last good check

priced tools
0

of 17 tools

_ answered our checks, 90 days 130 checks · signed record
  • unknown → live
_ what it is for
topic
communication chat & messaging
used for
  • set up a website live chat widget
  • train the support bot on a website
  • reply to a support conversation
  • list support conversations
  • configure the ai support agent
takes → gives
text → text, data
tools
10 reads6 changes data1 sends messages
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 17 tools
13 auth-required 4 never probed 13 of 17 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_analytics reads auth-required 23h ago

    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).

    mcp-tool

    {
  "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)."
    }
  }
}
    arguments 13 lines
  • list_conversations reads auth-required 23h ago

    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/email and last message. Returns a compact list: id, contact name, status, unreadCount, last message preview, updatedAt.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 200,
      "description": "Max conversations to return (default 100).",
      "exclusiveMinimum": 0
    },
    "search": {
      "type": "string",
      "description": "Free-text match on contact name/email and the last message preview."
    },
    "status": {
      "enum": [
        "OPEN",
        "PENDING",
        "RESOLVED",
        "SNOOZED"
      ],
      "type": "string",
      "description": "Only conversations with this status."
    }
  }
}
    arguments 26 lines
  • singchat_setup changes data auth-required never probed

    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 returns a short-lived, single-use browser claim link plus the website embed snippet. The user chooses their own sign-in details in the browser; no reusable credentials are returned to the model. If a workspace is already authenticated, it returns THIS workspace's embed snippet and dashboard link (it never creates a duplicate workspace).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 120,
      "description": "Optional workspace/brand name for a newly created workspace. Ignored if a key is already set."
    }
  }
}
    arguments 11 lines
  • claim_account reads auth-required never probed

    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 so the user does not lose access. The link is single-use and expires after 15 minutes. Requires an authenticated legacy workspace.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • reply_to_conversation sends messages auth-required never probed

    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 agent inbox. Email, Telegram, and WhatsApp conversations are rejected before any change.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "conversationId",
    "content"
  ],
  "properties": {
    "content": {
      "type": "string",
      "minLength": 1,
      "description": "The reply text to send to the visitor."
    },
    "conversationId": {
      "type": "string",
      "minLength": 1,
      "description": "The conversation id to reply in."
    }
  }
}
    arguments 20 lines
  • resolve_conversation changes data auth-required never probed

    Mark a conversation as RESOLVED (closes it). The visitor's widget will no longer show it as active.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "conversationId"
  ],
  "properties": {
    "conversationId": {
      "type": "string",
      "minLength": 1,
      "description": "The conversation id to resolve."
    }
  }
}
    arguments 14 lines
  • add_knowledge changes data auth-required never probed

    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.

    mcp-tool

    {
  "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'."
    }
  }
}
    arguments 30 lines
  • configure_agent changes data auth-required never probed

    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 fields to just read back the current configuration. Does not touch or return any API keys.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "model": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1,
      "description": "Chat model id, e.g. gpt-4o-mini."
    },
    "enabled": {
      "type": "boolean",
      "description": "Turn the automated AI agent on (true) or off (false)."
    },
    "providerMode": {
      "enum": [
        "platform",
        "byok"
      ],
      "type": "string",
      "description": "'platform' = platform-hosted keys (billed via AI credits); 'byok' = bring your own key."
    },
    "systemPrompt": {
      "type": "string",
      "maxLength": 8000,
      "minLength": 1,
      "description": "The agent's system prompt / persona and answering rules."
    },
    "greetingMessage": {
      "type": "string",
      "maxLength": 2000,
      "description": "First message visitors see when they open the chat. Pass an empty string to clear it."
    }
  }
}
    arguments 35 lines
  • set_keywords changes data auth-required never probed

    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. keyword 'invoice' -> 'Download it from the billing page').

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "keywords",
    "reply"
  ],
  "properties": {
    "reply": {
      "type": "string",
      "maxLength": 2000,
      "minLength": 1,
      "description": "The reply text to send."
    },
    "keywords": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 80,
        "minLength": 1
      },
      "maxItems": 20,
      "minItems": 1,
      "description": "Trigger words/phrases (case-insensitive)."
    },
    "matchType": {
      "enum": [
        "CONTAINS",
        "EXACT"
      ],
      "type": "string",
      "description": "CONTAINS (default) = keyword appears anywhere in the message; EXACT = whole message equals the keyword."
    }
  }
}
    arguments 35 lines
  • manage_faq changes data auth-required never probed

    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' | 'delete'. 'create' needs `question` + `answer`; 'update' and 'delete' need `id`.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "action"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "FAQ item id. Required for 'update' and 'delete'."
    },
    "action": {
      "enum": [
        "list",
        "create",
        "update",
        "delete"
      ],
      "type": "string",
      "description": "Which FAQ operation to run."
    },
    "answer": {
      "type": "string",
      "maxLength": 4000,
      "minLength": 1,
      "description": "Answer text. Required for 'create'; optional for 'update'."
    },
    "enabled": {
      "type": "boolean",
      "description": "Whether the FAQ item is visible/active. Optional for 'create' and 'update'."
    },
    "question": {
      "type": "string",
      "maxLength": 500,
      "minLength": 1,
      "description": "Question text. Required for 'create'; optional for 'update'."
    }
  }
}
    arguments 39 lines
  • ping reads auth-required never probed

    Health check for the SingChat MCP server. Returns 'pong' and whether this request is authenticated to a workspace.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • list_knowledge reads auth-required 7h ago

    List all knowledge documents for this workspace with their processing status (PENDING | PROCESSING | READY | FAILED) and chunk counts. Use this to check whether items added via add_knowledge have finished training.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_embed_snippet reads auth-required 23h ago

    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 a workspace API key. Optionally pass `platform` to get just one flavor.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "platform": {
      "enum": [
        "html",
        "react",
        "next"
      ],
      "type": "string",
      "description": "Which snippet to return. Omit to get all three."
    }
  }
}
    arguments 15 lines
  • fetch reads unknown 7h ago

    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.

    mcp-tool

    {
  "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."
    }
  }
}
    arguments 13 lines
  • search reads unknown 5h ago

    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 own help content (what SingChat is, adding the chat widget, MCP setup, free tier, AI training, channels, white label, pricing). Returns a list of results with id, title, and url. Use the fetch tool with a result id to read the full text.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "The search query or user question."
    }
  }
}
    arguments 13 lines
  • search_knowledge reads unknown 5h ago

    Semantic search over the workspace knowledge base. Returns the most relevant chunks (with source document title and similarity score) for a query. Only searches documents that have finished training (status READY).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "topK": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "Max number of chunks to return (default 5)."
    },
    "query": {
      "type": "string",
      "minLength": 1,
      "description": "The search query / user question."
    }
  }
}
    arguments 20 lines
  • get_conversation reads unknown 7h ago

    Fetch a single conversation with its contact details and the most recent messages (oldest→newest).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "conversationId"
  ],
  "properties": {
    "conversationId": {
      "type": "string",
      "minLength": 1,
      "description": "The conversation id (from list_conversations)."
    }
  }
}
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id bd1327aae9b8354d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/bd1327aae9b8354d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/bd1327aae9b8354d/badge.svg)](https://brick.blue/agent/bd1327aae9b8354d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on singchat.org 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.