Home / MCP registry index / digital.chip-ai/chip
Chip MCP
digital.chip-ai/chip in the official MCP registry.
Endpoint https://chip-ai.digital/mcp/. Source: github.com/zapret-digital/chip-mcp.
The registry describes it as: Project memory, tasks and Telegram notifications for your coding agent. Chip account required.
We read its 27 tools on 2026-10-22. 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
whoami list_projects read_journal read_project_dialog get_project_map read_map_section get_project_context search_project list_files read_project_file create_project rename_project archive_project save_session_summary add_note whats_new list_tasks complete_task add_task notify_me set_reminder ask_user check_confirmation upload_project_file finalize_upload attach_file generate_image
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/digital-chip-ai-chip)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.