Home / MCP registry index / eu.autosignal/autosignal

AutoSignal

eu.autosignal/autosignal in the official MCP registry. Endpoint https://api.autosignal.eu/mcp.

The registry describes it as: Czech and Central European used and new car market prices, valuations and below-market deals.

We read its 16 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

search_deals get_deal list_hot_deals list_recently_reduced list_brands list_models list_countries get_market_trend get_price_history estimate_valuation get_weekly_summary get_market_overview get_price_movers check_vehicle_by_vin search_company_fleets get_company_fleet

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

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.