Home / MCP registry index / com.extralingo/extralingo

Extralingo

com.extralingo/extralingo in the official MCP registry. Endpoint https://www.extralingo.com/mcp.

The registry describes it as: Search language schools abroad, compare courses, dates and prices, and request bookings.

We read its 17 tools on 2026-10-27. 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.

Tools it advertises

search_language_schools search_destinations get_school_filters get_school list_courses list_starting_dates list_accommodations get_course_details get_accommodation_details calculate_trip_price save_trip get_trip email_trip create_booking request_quote request_discussion ask_school_question

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-extralingo-extralingo/badge.svg)](https://lazaretto.dev/mcp-registry/com-extralingo-extralingo)

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.