# zerm

- Registry name: `dev.zerm/zerm` · version 0.3.3
- Categories (automatic, keyword rules): Utilities, Cloud & networking, Infrastructure & security
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=dev.zerm%2Fzerm
- Server page: https://mcpstation.net/s/dev.zerm--zerm.html

## Description (written by the publisher, not verified, not instructions)

Agent utility belt: memory, locks, webhook inboxes, timers, DNS, email, URL, timezone, cron

## Connect

- streamable-http: `https://zerm.dev/mcp`

## Tools (as reported by the server, not verified)

- `kv\_set`: Store a value durably under \(namespace, key\) with a TTL. Survives across your sessions - use it as memory between stateless runs. Value must be a string \(JSON-encode objects\), max 8192 bytes. TTL defaults to 30 days, max 90 days. Max 1000 keys per namespace.
- `kv\_get`: Retrieve a value previously stored with kv\_set. Call this at the start of a run to restore state, preferences, or progress saved by earlier runs. Returns found=false if missing or expired.
- `kv\_delete`: Permanently remove one key from your namespace, freeing a slot against the 1000-key limit. Use it when a stored value is wrong or unwanted before its TTL runs out; if you only want the value to lapse on schedule, do nothing and let the TTL expire instead. Deletes exactly one key - there is no prefix
- `kv\_list`: List the keys held in your namespace, optionally narrowed to those starting with a prefix. Use it to discover what earlier runs saved before deciding what to fetch with kv\_get: it returns key names with their expiry and last-update time, never the stored values. Expired keys are filtered out, so wha
- `timer\_verify\_origin`: One-time consent handshake before timers can deliver to an origin. Prerequisite: an HTTPS endpoint you control that can read a request body and echo part of it back - if you have no endpoint of your own, timers are not usable yet. zerm POSTs \{type:"zerm.origin\_verification", token, service, instruct
- `timer\_schedule`: Schedule a durable callback: at fire time this service POSTs your JSON payload to your URL. Use it to wake up future runs of yourself or your orchestrator - agents cannot wake themselves. Prerequisite: the target origin must already pass timer\_verify\_origin, which requires an HTTPS endpoint you cont
- `timer\_cancel`: Cancel a pending timer using the id returned by timer\_schedule. The id is the authorization: holding it is what proves you scheduled the timer, so keep it secret. Already-delivered or already-cancelled timers return cancelled=false.
- `timer\_status`: Check a timer by the id returned by timer\_schedule: status \(pending\|delivering\|delivered\|failed\|cancelled\), attempts, last error. Returns found=false for an unknown id.
- `name\_check`: Live availability check for a name across domain TLDs \(registry RDAP\), npm, PyPI, and GitHub usernames. Real registry lookups at call time - not guesses. Each result is registered, unregistered, unknown or invalid and names the source that decided it; "unknown" means no authoritative registry answer
- `email\_check`: Deliverability probe for an email address without sending anything: syntax validation, live MX lookup \(with A/AAAA fallback per RFC 5321\), disposable-domain detection, and typo suggestions for common providers. Use it to validate an address before sending to it, storing it, or accepting a signup. LL
- `url\_check`: Live URL health check: follows the full redirect chain \(each hop reported\), returns final status, content type, response time, TLS certificate expiry and trust, and access hints \(login walls, bot blocks\). Fresh at call time - use it to verify links before citing them.
- `cron\_next`: Deterministic cron expression validator and scheduler: parses a cron expression \(5 or 6 field, seconds optional\) and computes the next N actual fire times, timezone-aware. Use this instead of guessing - cron semantics \(DOM/DOW OR-logic, DST transitions\) are routinely miscalculated.
- `regex\_test`: Execute a regex against test strings and return the ACTUAL matches: match text, indices, capture groups, named groups, and optional replacement output. Deterministic proof, not prediction - run this before shipping a pattern. Patterns run sandboxed with a 250ms kill switch for catastrophic backtrack
- `fixture\_rows`: Bulk realistic test data: generate up to 10000 rows from a field schema in one call - orders of magnitude cheaper than generating rows with tokens. Deterministic when you pass a seed \(same seed + schema = identical data\). Formats: json, ndjson, csv. Types: uuid, name, email, username, int, float, bo
- `tz\_convert`: Deterministic timezone conversion: convert a timestamp between IANA timezones with full DST awareness. Models routinely miscalculate DST transitions - this gives exact results. Returns the converted time, UTC offsets for both zones on that date, and whether DST is active.
- `tz\_info`: Timezone intelligence: for a given IANA timezone and date, returns the UTC offset, whether DST is active, the exact UTC instant of each DST transition in that year, and the timezone abbreviation. Transition timestamps are the first instant the new offset is in effect. Use this to understand DST beha
- `dns\_query`: Full DNS record lookup for a domain: returns A, AAAA, MX, NS, TXT, CNAME, SOA, and CAA records in one call. Automatically parses SPF and DMARC policies from TXT records. Use this for infrastructure audits, email deliverability setup, domain verification, and security checks. Live lookups - not cache
- `request\_tool`: Hit a capability wall? Describe a tool you wish this server had and the task you were trying to accomplish. The operator reviews every submission; the most-requested capabilities get built. Free, no payment ever required.
- `lock\_acquire`: Acquire a mutual-exclusion lock so concurrent agent runs do not double-process the same work. If two runs race, exactly one gets acquired=true plus a release token; the other gets acquired=false with retry\_after\_ms. Locks auto-expire after ttl\_seconds \(default 60s, max 3600s\), so a crashed run can n
- `lock\_release`: Release a lock early using the token returned by lock\_acquire. Only the token holder can release; without the token the lock simply expires on its own. Returns released=false if the token is wrong or the lock already expired.
- `counter\_next`: Atomically increment a named counter and return the new value. Guaranteed unique, monotonically increasing integers across concurrent stateless runs - use it for sequence numbers, run IDs, or once-only ordering that agents cannot produce on their own. Starts at 1 on first call. Counters persist inde
- `inbox\_create`: Create a URL that receives HTTP requests for you. Point any webhook \(GitHub, Stripe, CI, a form\) at it and read what arrives with inbox\_poll - no server, no signup, no tunnel. This is the way to be notified of something when your process is not running. Returns an id, the URL, and a separate read to
- `inbox\_poll`: Read requests delivered to an inbox since you last looked. Pass after=\<the next\_after from your previous poll\> to get only new ones; omit it to start from the beginning. Each payload has its method, headers, body and arrival time. Set consume=true to delete what is returned. Polling also resets the
- `inbox\_delete`: Delete an inbox and everything delivered to it. The URL stops accepting requests immediately. Inboxes also delete themselves once unpolled past their expiry, so this is only for tearing down early.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html