Kayako MCP by usefulapi
io.usefulapi/kayakousefulapi.iostreamable-httpv1.40.4Scanned
Search Kayako cases, replies, customers and help-center articles, and reply to or create cases.
21 tools: 5 can delete or cancel things and 16 only read.
- Reads private data · 9
- Reads text others write · 9
- Can send data out · 1
- 1 finding
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
5 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Kayako MCP by usefulapi can do
The Kayako MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 21 tools. It can delete or cancel things (5 tools: kayako_create_case, kayako_update_case, kayako_reply_to_case, kayako_add_case_tags and 1 more). 16 tools only read.
9 tools read private data (kayako_get_me, kayako_list_cases, kayako_get_case and 6 more); 9 tools bring in text other people can write (kayako_list_cases, kayako_get_case, kayako_list_case_posts and 6 more); 1 tool can send data out of your system (kayako_reply_to_case). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.
Last scanned Oct 25, 2026, version 1.40.4.
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.
21 tools
Deletes or cancels 5Claude Code: deny
kayako_add_case_tagsWRITE: add tags to a case, keeping its existing tags.No findings
Why it is in this group
- The name "kayako_add_case_tags" says "add": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it WRITE: add tags to a case, keeping its existing tags. Kayako: POST /api/v1/cases/{id}/tags.json.
Annotations the server declares
- title: Add tags to a case
- destructiveHint: true
kayako_create_caseWRITE: open a new case (conversation) for a requester.No findings
Why it is in this group
- The name "kayako_create_case" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it WRITE: open a new case (conversation) for a requester. channel MAIL sends the first message to the customer by email from the mailbox given as channel_id; channel NOTE creates it with an internal note and emails nobody. Get channel ids from kayako_list_channels and status/priority/type ids from kayako_list_case_options. Kayako: POST /api/v1/cases.json.
Annotations the server declares
- title: Create a case
- destructiveHint: true
kayako_create_userWRITE: create a user — typically a CUSTOMER to use as requester_id on a new case.No findings
Why it is in this group
- The name "kayako_create_user" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it WRITE: create a user — typically a CUSTOMER to use as requester_id on a new case. role_id comes from kayako_list_roles. Collaborator/agent/admin roles also require email and team_ids. No password is set by this tool. Kayako: POST /api/v1/users.json.
Annotations the server declares
- title: Create a user
- destructiveHint: true
kayako_reply_to_caseWRITE: add a post to a case.Can send data outNo findings
Why it is in this group
- The name "kayako_reply_to_case" says "reply": a word for sending, and what is sent cannot be taken back.
- The server marks it destructive (destructiveHint: true).
What it can reach
- outboundThe name "kayako_reply_to_case" says "reply": it sends or publishes something to other people.
Description, as the server wrote it WRITE: add a post to a case. channel NOTE adds an INTERNAL note visible only to agents (no channel_id needed). channel MAIL/TWITTER/FACEBOOK sends a PUBLIC reply to the customer — get channel_id from kayako_list_channels with case_id. Can also set status/priority/assignee in the same call. Kayako: POST /api/v1/cases/{id}/reply.json.
Annotations the server declares
- title: Reply to a case or add an internal note
- destructiveHint: true
kayako_update_caseWRITE: change a case's subject, requester, assignee (team/agent), status, priority, type, brand, form, tags or custom fields.No findings
Why it is in this group
- The name "kayako_update_case" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it WRITE: change a case's subject, requester, assignee (team/agent), status, priority, type, brand, form, tags or custom fields. Sends nothing to the customer. `tags` sets the case's tag list (use kayako_add_case_tags to append). Trashing is deliberately not exposed. Kayako: PUT /api/v1/cases/{id}.json.
Annotations the server declares
- title: Update a case
- destructiveHint: true
Only reads 16Show 16 read-only tools
kayako_get_articleFetch one knowledge-base article with its localized titles and contents expanded (include defaults to 'locale_field'), status, section, tags, votes and help-center URL.Reads text others writeNo findings
Why it is in this group
- The name "kayako_get_article" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Fetch one knowledge-base article with its localized titles and contents expanded (include defaults to 'locale_field'), status, section, tags, votes and help-center URL. Kayako: GET /api/v1/articles/{id}.json.
Annotations the server declares
- title: Get a help-center article
- readOnlyHint: true
kayako_get_caseFetch one case (conversation) by id: subject, requester, assignee, status, priority, type, SLA metrics, custom fields, last post preview.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "kayako_get_case" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "fetch" and "conversation": it reads messages.
- untrusted-inputThe description's first sentence says "fetch" and "conversation": it reads messages, which other people can write.
Description, as the server wrote it Fetch one case (conversation) by id: subject, requester, assignee, status, priority, type, SLA metrics, custom fields, last post preview. Use include (e.g. 'user,case_status,case_priority,team') to expand references and fields='+tags' for tags. Kayako: GET /api/v1/cases/{id}.json.
Annotations the server declares
- title: Get a case
- readOnlyHint: true
kayako_get_meFetch the Kayako user these credentials belong to (name, role, teams, locale).Reads private data1 finding
Why it is in this group
- The name "kayako_get_me" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "fetch" and "credential": it reads secrets.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "Fetch the Kayako user these credentials belong to (name, role, teams, locale)...."
Description, as the server wrote it Fetch the Kayako user these credentials belong to (name, role, teams, locale). A cheap way to confirm the subdomain and credentials work. Kayako: GET /api/v1/me.json.
Annotations the server declares
- title: Get the current user
- readOnlyHint: true
kayako_get_userFetch one user by id: name, role, organization, teams, identities (emails, phones, social), custom fields.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "kayako_get_user" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "fetch" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "fetch" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it Fetch one user by id: name, role, organization, teams, identities (emails, phones, social), custom fields. include='identity_email,organization' expands references. Kayako: GET /api/v1/users/{id}.json.
Annotations the server declares
- title: Get a user
- readOnlyHint: true
kayako_list_articlesList knowledge-base articles, optionally by section, tags, or PUBLISHED / PINNED.No findings
Why it is in this group
- The name "kayako_list_articles" says "list": a word for reading.
Description, as the server wrote it List knowledge-base articles, optionally by section, tags, or PUBLISHED / PINNED. Titles and contents are locale references unless include='locale_field'. Kayako: GET /api/v1/articles.json.
Annotations the server declares
- title: List help-center articles
- readOnlyHint: true
kayako_list_case_optionsList the instance's case statuses (id, label, type), priorities (id, label, level) or types (id, label, type) — the ids needed for status_id / priority_id / type_id when creating, …No findings
Why it is in this group
- The name "kayako_list_case_options" says "list": a word for reading.
Description, as the server wrote it List the instance's case statuses (id, label, type), priorities (id, label, level) or types (id, label, type) — the ids needed for status_id / priority_id / type_id when creating, updating or replying to a case. Kayako: GET /api/v1/cases/{statuses|priorities|types}.json.
Annotations the server declares
- title: List case statuses, priorities or types
- readOnlyHint: true
kayako_list_case_postsRead a case's timeline: customer messages, agent replies and internal notes (newest first).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "kayako_list_case_posts" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "message": it reads messages.
- untrusted-inputThe name "kayako_list_case_posts" says "list" and "post": it reads posts, which other people can write.
- untrusted-inputThe description's first sentence says "read" and "message": it reads messages, which other people can write.
Description, as the server wrote it Read a case's timeline: customer messages, agent replies and internal notes (newest first). By default activities are excluded; filters='NOTES' for internal notes only, 'MESSAGES' for messages, 'ALL' to include activities. Paginate with before_id / after_id (one at a time). Kayako: GET /api/v1/cases/{id}/posts.json.
Annotations the server declares
- title: List a case's posts
- readOnlyHint: true
kayako_list_casesList cases (conversations / tickets), newest-updated first.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "kayako_list_cases" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "conversation": it reads messages.
- untrusted-inputThe description's first sentence says "list" and "conversation": it reads messages, which other people can write.
Description, as the server wrote it List cases (conversations / tickets), newest-updated first. Filter by status type, tags, max priority level, or a requester identity (email, Twitter screen name, Facebook username, phone); or fetch specific ids. Nested resources are references unless `include` expands them. Kayako: GET /api/v1/cases.json.
Annotations the server declares
- title: List cases
- readOnlyHint: true
kayako_list_channelsList the channels (MAIL mailbox, TWITTER, FACEBOOK, NOTE) usable for a reply on an existing case (pass case_id) or for a new case (omit case_id; optionally pass the requester's use…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "kayako_list_channels" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "mail": it reads mail.
- untrusted-inputThe description's first sentence says "list" and "mail": it reads inbound email, which other people can write.
Description, as the server wrote it List the channels (MAIL mailbox, TWITTER, FACEBOOK, NOTE) usable for a reply on an existing case (pass case_id) or for a new case (omit case_id; optionally pass the requester's user_id). A channel's account.id is the channel_id to pass to kayako_reply_to_case / kayako_create_case. Kayako: GET /api/v1/cases/{id}/reply/channels.json or GET /api/v1/cases/channels.json.
Annotations the server declares
- title: List reply channels
- readOnlyHint: true
kayako_list_organization_casesList the cases (conversations) raised by members of one organization, newest-updated first.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "kayako_list_organization_cases" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "conversation": it reads messages.
- untrusted-inputThe description's first sentence says "list" and "conversation": it reads messages, which other people can write.
Description, as the server wrote it List the cases (conversations) raised by members of one organization, newest-updated first. Kayako: GET /api/v1/organizations/{id}/cases.json.
Annotations the server declares
- title: List an organization's cases
- readOnlyHint: true
kayako_list_organizationsList customer organizations (name, domains, phone, custom fields), oldest first.No findings
Why it is in this group
- The name "kayako_list_organizations" says "list": a word for reading.
Description, as the server wrote it List customer organizations (name, domains, phone, custom fields), oldest first. To find one by name use kayako_search with resources=['ORGANIZATIONS']. Kayako: GET /api/v1/organizations.json.
Annotations the server declares
- title: List organizations
- readOnlyHint: true
kayako_list_rolesList user roles (id, title, type OWNER/ADMIN/AGENT/COLLABORATOR/CUSTOMER) — the role_id needed by kayako_create_user.No findings
Why it is in this group
- The name "kayako_list_roles" says "list": a word for reading.
Description, as the server wrote it List user roles (id, title, type OWNER/ADMIN/AGENT/COLLABORATOR/CUSTOMER) — the role_id needed by kayako_create_user. Kayako: GET /api/v1/roles.json.
Annotations the server declares
- title: List roles
- readOnlyHint: true
kayako_list_teamsList agent teams (id, title, member count) — the ids for assigned_team_id.No findings
Why it is in this group
- The name "kayako_list_teams" says "list": a word for reading.
Description, as the server wrote it List agent teams (id, title, member count) — the ids for assigned_team_id. Kayako: GET /api/v1/teams.json.
Annotations the server declares
- title: List teams
- readOnlyHint: true
kayako_list_usersList users (customers, collaborators, agents, admins), newest first, optionally by role type or specific ids.No findings
Why it is in this group
- The name "kayako_list_users" says "list": a word for reading.
Description, as the server wrote it List users (customers, collaborators, agents, admins), newest first, optionally by role type or specific ids. To find a user by email or name use kayako_search. Kayako: GET /api/v1/users.json.
Annotations the server declares
- title: List users
- readOnlyHint: true
kayako_searchUnified search across conversations (cases), users and organizations.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "kayako_search" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "conversation": it reads messages.
- untrusted-inputThe description's first sentence says "conversation": it reads messages, which other people can write.
Description, as the server wrote it Unified search across conversations (cases), users and organizations. Returns id, title, snippet, relevance and resource type; pass fields='*' to get each full resource inline. Max 30 results. Kayako: GET /api/v1/search.json.
Annotations the server declares
- title: Search cases, users and organizations
- readOnlyHint: true
kayako_search_help_centerSearch the help center's articles and/or public conversations.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "kayako_search_help_center" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "search" and "conversation": it reads messages.
- untrusted-inputThe description's first sentence says "search" and "conversation": it reads messages, which other people can write.
Description, as the server wrote it Search the help center's articles and/or public conversations. Returns references (e.g. {id, resource_type: 'article'}); read an article with kayako_get_article. Kayako: GET /api/v1/helpcenter/search.json.
Annotations the server declares
- title: Search the help center
- readOnlyHint: true
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.
81 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data9
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write9
- 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.
{
"permissions": {
"deny": [
"mcp__kayako__kayako_reply_to_case"
]
}
}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, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- 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
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 5 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://kayako.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://kayako.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
- Infokayako_get_me
The description mentions "credentials".
What this check looks forMatched text
description: "Fetch the Kayako user these credentials belong to (name, role, teams, locale)...."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 5 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://kayako.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://kayako.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http kayako https://kayako.usefulapi.io/mcpclaude mcp add --transport http kayako https://kayako.usefulapi.io/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__kayako__kayako_get_me",
"mcp__kayako__kayako_list_cases",
"mcp__kayako__kayako_get_case",
"mcp__kayako__kayako_list_case_posts",
"mcp__kayako__kayako_list_channels",
"mcp__kayako__kayako_list_case_options",
"mcp__kayako__kayako_search",
"mcp__kayako__kayako_list_users",
"mcp__kayako__kayako_get_user",
"mcp__kayako__kayako_list_organizations",
"mcp__kayako__kayako_list_organization_cases",
"mcp__kayako__kayako_list_teams",
"mcp__kayako__kayako_list_roles",
"mcp__kayako__kayako_list_articles",
"mcp__kayako__kayako_get_article",
"mcp__kayako__kayako_search_help_center"
],
"ask": [],
"deny": [
"mcp__kayako__kayako_create_case",
"mcp__kayako__kayako_update_case",
"mcp__kayako__kayako_reply_to_case",
"mcp__kayako__kayako_add_case_tags",
"mcp__kayako__kayako_create_user"
]
}
}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 kayako. Review it before you use it.
Capability tags behind 11 rules
- mcp__kayako__kayako_get_me private-data
- mcp__kayako__kayako_list_cases private-data, untrusted-input
- mcp__kayako__kayako_get_case private-data, untrusted-input
- mcp__kayako__kayako_list_case_posts private-data, untrusted-input
- mcp__kayako__kayako_list_channels private-data, untrusted-input
- mcp__kayako__kayako_search private-data, untrusted-input
- mcp__kayako__kayako_get_user private-data, untrusted-input
- mcp__kayako__kayako_list_organization_cases private-data, untrusted-input
- mcp__kayako__kayako_get_article untrusted-input
- mcp__kayako__kayako_search_help_center private-data, untrusted-input
- mcp__kayako__kayako_reply_to_case outbound
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/io.usefulapi/kayako/verify?hash=dfa11c7e6009b21d6e6a9ac3f67350afd75a6a7a9a879467a3ffa892cb490544" | jq -e '.changed == false'Pinned hash dfa11c7e6009, from Oct 25, 2026, 23:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/kayako/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/kayako)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
Kayako MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Kayako MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 21 tools, 5 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Kayako MCP by usefulapi delete data?
- Yes. 5 tools can delete, cancel or revoke something: kayako_create_case, kayako_update_case, kayako_reply_to_case, kayako_add_case_tags and kayako_create_user.
Can the Kayako MCP by usefulapi 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 Kayako MCP by usefulapi have?
- 21 tools: 5 destructive, 16 read. kayako_create_case, kayako_update_case, kayako_reply_to_case, kayako_add_case_tags, kayako_create_user, kayako_get_me, kayako_list_cases, kayako_get_case and 13 more.
Does the Kayako MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Kayako MCP by usefulapi send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): kayako_reply_to_case.
Has the Kayako MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.