CallChatSyn MCP server
com.callchatsyn/callchatsyncallchatsyn.comstreamable-httpv0.1.0Scanned
Answer small-business customer questions from FAQs, list open appointment times, and book them.
4 tools: 1 can delete or cancel things, 2 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the CallChatSyn MCP server can do
The CallChatSyn MCP server is published by callchatsyn.com, a domain the MCP Registry verified. It has 4 tools. It can delete or cancel things (1 tool: cancel_appointment) and create or change data (2 tools: answer_customer_question and book_appointment). 1 tool only reads.
2 tools bring in text other people can write (book_appointment and cancel_appointment); 1 tool can send data out of your system (book_appointment).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Deletes or cancels 1Claude Code: deny
cancel_appointmentCancel one of the business's bookings by the 'id' that book_appointment returned.Reads text others writeNo findings
Why it is in this group
- The name "cancel_appointment" says "cancel": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Cancel one of the business's bookings by the 'id' that book_appointment returned. This changes data: the time becomes free again, and if the business has connected Cal.com the booking is cancelled there too (Cal.com emails the customer). Only call it after the customer has clearly asked to cancel that specific booking. To reschedule, cancel and then book a new time from list_open_times. With the demo key it's a dry run. Errors: 404 no such booking for this business, 409 already cancelled, 400 not a booking id. Returns JSON { cancelled, id, start }.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
Changes things 2Claude Code: ask
answer_customer_questionAnswer a customer's message for one small business using only that business's own FAQs and order records.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Answer a customer's message for one small business using only that business's own FAQs and order records. Rule-based, not generated, so it never invents prices or opening hours; English and Chinese are detected automatically. Read-only: it never books or changes anything. Use it first for any customer message. If it returns intent 'appointment', call list_open_times next; if matched is false or intent is 'human_handoff', tell the customer a person will follow up. Authenticates with the connection's API key (Authorization: Bearer ccs_live_…); without a key it answers as a public demo business. Returns JSON { intent, lang, matched, reply, next? }.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
book_appointmentBook one appointment for a customer.Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
Description, as the server wrote it Book one appointment for a customer. This creates a real booking: the business is notified, and if it has connected Cal.com the booking is created there too. With the demo key it's a dry run that books nothing. Not idempotent: booking the same time twice fails the second time. Only call it after the customer has confirmed the time and service; needs a 'start' from list_open_times and the customer's email or phone. Errors: 404 the time is no longer offered (call list_open_times again), 409 it was just taken, 400 missing start, service, or both email and phone, or the business's connected calendar needs a detail the customer didn't give (the message says which, e.g. an email). Returns JSON { booked, id, start, label }; keep 'id' if the customer may want to cancel.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 1Show 1 read-only tool
list_open_timesList the business's next open appointment times: up to 5, soonest first, within the next 7 days, labelled in the business's time zone, plus its services and locations.No findings
Why it is in this group
- The name "list_open_times" says "list": a word for reading.
Description, as the server wrote it List the business's next open appointment times: up to 5, soonest first, within the next 7 days, labelled in the business's time zone, plus its services and locations. Read-only. Call it before book_appointment and whenever a customer asks when they can come in. Times come from the business's CallChatSyn hours or from its connected Cal.com calendar. Returns JSON { slots: [{ start, label }], services, locations }; pass a slot's 'start' to book_appointment unchanged. An empty slots list means nothing is open this week.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:35 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://callchatsyn.com/api/mcp: tools/list returned 4 tools to an anonymous client, including cancel_appointment (destructive), answer_customer_question (write), book_appointment (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http callchatsyn https://callchatsyn.com/api/mcpclaude mcp add --transport http callchatsyn https://callchatsyn.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__callchatsyn__list_open_times"
],
"ask": [
"mcp__callchatsyn__answer_customer_question",
"mcp__callchatsyn__book_appointment"
],
"deny": [
"mcp__callchatsyn__cancel_appointment"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as callchatsyn. Review it before you use it.
Capability tags behind 2 rules
- mcp__callchatsyn__book_appointment untrusted-input, outbound
- mcp__callchatsyn__cancel_appointment untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.callchatsyn/callchatsyn/verify?hash=fd94626385e77b71688437e19799deb116246ef934a051ab3b654d0cd61f164c" | jq -e '.changed == false'Pinned hash fd94626385e7, from Nov 10, 2026, 12:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.callchatsyn/callchatsyn/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.callchatsyn/callchatsyn)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:52 UTC.
CallChatSyn MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the CallChatSyn MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the CallChatSyn MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: cancel_appointment.
Can the CallChatSyn MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the CallChatSyn MCP server have?
- 4 tools: 1 destructive, 2 write, 1 read. cancel_appointment, answer_customer_question, book_appointment and list_open_times.
Does the CallChatSyn MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the CallChatSyn MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): book_appointment.
Has the CallChatSyn MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.