Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Kaio

REMOTE · API.WEBSITE.PROD.AKAION.COM

Find and book local businesses in Italy on Kaio: real free times, booking, online payment link.

0 this week 81 Trust /100

Last scanned (12 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Productivity and Notes

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 726 tokens (~145/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://api.website.prod.akaion.com/mcp/kaio

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.website.prod.akaion.com CN=WR3,O=Google Trust Services,C=US 6 Oct 2026 4 Jan 2027 RSA 2048 SHA256-RSA 42e6309f9392049d0abde1c970c198a5
SANs: api.website.prod.akaion.com
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.website.prod.akaion.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
akaion.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.website.prod.akaion.com/mcp/kaio Verified 200
http (plaintext) http://api.website.prod.akaion.com/mcp/kaio HTTPS enforced 302 https://api.website.prod.akaion.com/mcp/kaio
MCP tools · 5 exposed · ~551 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
book_kaio_appointment ~127

Book an appointment at a Kaio business. `start_time` is one of the slots from kaio_free_slots (ISO 8601 with offset). A phone or an email is required: the business uses it to confirm and remind. Only call this after the person has confirmed business, service, day, time and contact details.

NameTypeReqDescription
email–––
namestringyes–
notes–––
phone–––
service_idstringyes–
slugstringyes–
start_timestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_kaio_business ~64

A Kaio business by its slug (from search_kaio_businesses): description, timezone, booking link and services with their ids, duration and price — the ids are what kaio_free_slots and booking need.

NameTypeReqDescription
slugstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

kaio_free_slots ~87

Real free times of a Kaio business for one service (id from get_kaio_business), dates YYYY-MM-DD, at most a couple of weeks at a time. These are the same slots its booking page shows.

NameTypeReqDescription
end_datestringyes–
service_idstringyes–
slugstringyes–
start_datestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

request_kaio_appointment ~173

Leave a request at a Kaio business for a service marked on_request (get_kaio_business): no slot is picked, the owner calls back to fix day and time. `description`: what is needed (job, address or area, sizes…); `preferred_time`: free text ("mattina", "dopo le 17", "settimana prossima"). A phone or an email is required. First recap business, service, description, preferred time and contact details to the person, and call this only after they say yes.

NameTypeReqDescription
description–––
email–––
namestringyes–
phone–––
preferred_time–––
service_idstringyes–
slugstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

search_kaio_businesses ~100

Find businesses that can be booked online with Kaio. `what`: the kind of business or treatment ("estetista", "pulizia viso", "idraulico"); `where`: town, province or area ("Lecco", "Brianza"). Returns name, slug, address, Google rating, website, booking link and services with prices.

NameTypeReqDescription
whatstring––
wherestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the Kaio MCP server?

Kaio is a hosted endpoint at https://api.website.prod.akaion.com/mcp/kaio, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.website.prod.akaion.com

# add to Claude Code
claude mcp add --transport http com-akaion-kaio 'https://api.website.prod.akaion.com/mcp/kaio'
Common questions

What is the Kaio MCP server?

Kaio is an MCP server listed in the public MCP registry as com.akaion/kaio. Find and book local businesses in Italy on Kaio: real free times, booking, online payment link. This page covers its hosted endpoint (https://api.website.prod.akaion.com/mcp/kaio).

Is the Kaio MCP server safe to use?

Kaio scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Kaio MCP server expose?

Kaio exposes 5 tools: search_kaio_businesses, get_kaio_business, kaio_free_slots, book_kaio_appointment, request_kaio_appointment. Their descriptions and schemas cost roughly 551 tokens of context every time the server is loaded.

Does the Kaio MCP server require authentication?

No. We connected to Kaio without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Kaio MCP server still maintained?

Kaio is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Kaio MCP server?

VerifyMCP ran 13 checks on Kaio, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.