Home / MCP registry index / io.usefulapi/kayako

Kayako MCP by usefulapi

io.usefulapi/kayako in the official MCP registry. Endpoint https://kayako.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: Search Kayako cases, replies, customers and help-center articles, and reply to or create cases.

We read its 21 tools on 2026-10-31. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http kayako https://kayako.usefulapi.io/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "kayako": {
      "url": "https://kayako.usefulapi.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"kayako","type":"http","url":"https://kayako.usefulapi.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

kayako_get_me kayako_list_cases kayako_get_case kayako_list_case_posts kayako_list_channels kayako_list_case_options kayako_search kayako_list_users kayako_get_user kayako_list_organizations kayako_list_organization_cases kayako_list_teams kayako_list_roles kayako_list_articles kayako_get_article kayako_search_help_center kayako_create_case kayako_update_case kayako_reply_to_case kayako_add_case_tags kayako_create_user

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): 697b2e5f9c7092e5. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-usefulapi-kayako/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-kayako)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.