Home / MCP registry index / io.github.cigo240920/cigo-aircare
Cigo Aircare & Carsafe
io.github.cigo240920/cigo-aircare in the official MCP registry.
Endpoint https://cigo-mcp-system-wzoy.onrender.com/mcp. Source: github.com/cigo240920/Cigo-MCP-system.
The registry describes it as: 씨고 나노섬유 카세이프 맞춤 차량용 필터 규격 조회, 환경 리스크 진단 및 B2B 공조 솔루션
We read its 5 tools on 2026-10-26. 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_hvac_filter_info search_carsafe check_environment set_crm_lifecycle submit_b2b_inquiry
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-cigo240920-cigo-aircare)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.