Home / MCP registry index / com.kratons/public

com.kratons/public

com.kratons/public in the official MCP registry. Endpoint https://api.kratons.com/api/mcp.

The registry describes it as: Kratons, boutique DMC: bespoke trips in Spain, Portugal, Morocco. Facts, catalog, reviews, requests.

We read its 8 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.

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.

Tools it advertises

get_company_facts list_destinations search_experiences list_sample_itineraries get_reviews get_proposal_request_status how_to_request_a_proposal request_a_proposal

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-kratons-public/badge.svg)](https://lazaretto.dev/mcp-registry/com-kratons-public)

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.