Home / MCP registry index / dev.zerm/zerm
zerm
dev.zerm/zerm in the official MCP registry.
Endpoint https://zerm.dev/mcp.
The registry describes it as: Agent utility belt: memory, locks, webhook inboxes, timers, DNS, email, URL, timezone, cron
We read its 24 tools on 2026-10-22. 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
kv_set kv_get kv_delete kv_list timer_verify_origin timer_schedule timer_cancel timer_status name_check email_check url_check cron_next regex_test fixture_rows tz_convert tz_info dns_query request_tool lock_acquire lock_release counter_next inbox_create inbox_poll inbox_delete
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/dev-zerm-zerm)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.