zerm is a remote MCP server that gives an AI agent 24 tools, among them counter_next, cron_next, dns_query. It answers at https://zerm.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
Agent utility belt: memory, locks, webhook inboxes, timers, DNS, email, URL, timezone, cron
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 Inputs: namespace, name, key |
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 Inputs: expression, count, timezone, from |
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 Inputs: domain, types |
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 Inputs: email |
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, ndj Inputs: fields, count, seed, format |
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 |
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. Inputs: inbox_id, token |
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 consu Inputs: inbox_id, token, after, limit, consume |
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 Inputs: namespace, key |
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. Inputs: namespace, key |
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, ne Inputs: namespace, prefix, limit |
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 k Inputs: namespace, key, value, ttl_seconds |
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 Inputs: namespace, name, ttl_seconds |
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. Inputs: namespace, name, token |
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 Inputs: name, targets, tlds |
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 s Inputs: pattern, flags, tests, replacement |
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. Inputs: description, use_case |
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. Inputs: id |
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 ti Inputs: url, payload, delay_seconds, fire_at |
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. Inputs: id |
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 POST Inputs: url |
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 Inputs: datetime, timestamp, time, from, from_tz, to |
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 Inputs: timezone, date |
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 veri Inputs: url |
Every block below points at https://zerm.dev/mcp. Pick your client and copy.
claude mcp add --transport http zerm https://zerm.dev/mcp
{
"mcpServers": {
"zerm": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://zerm.dev/mcp"]
}
}
}{
"mcpServers": {
"zerm": {
"url": "https://zerm.dev/mcp"
}
}
}{
"servers": {
"zerm": {
"type": "http",
"url": "https://zerm.dev/mcp"
}
}
}{
"context_servers": {
"zerm": {
"url": "https://zerm.dev/mcp"
}
}
}{
"mcpServers": {
"zerm": {
"serverUrl": "https://zerm.dev/mcp"
}
}
}{
"mcpServers": {
"zerm": {
"url": "https://zerm.dev/mcp"
}
}
}name: zerm
version: 0.0.1
schema: v1
mcpServers:
- name: zerm
type: streamable-http
url: https://zerm.dev/mcp{
"mcpServers": {
"zerm": {
"httpUrl": "https://zerm.dev/mcp"
}
}
}{
"mcpServers": {
"zerm": {
"type": "http",
"url": "https://zerm.dev/mcp"
}
}
}{
"mcpServers": {
"zerm": {
"url": "https://zerm.dev/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fzerm.dev%2Fmcp&type=streamable_http&id=zerm&name=zerm
It answered our last check on 18 October 2026 in 502 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by zerm.dev and served from zerm.dev, the vendor's own domain: https://zerm.dev/mcp.
24, as returned by the server's own tools/list on 31 August 2026: counter_next, cron_next, dns_query, email_check, fixture_rows, inbox_create, inbox_delete, inbox_poll, and 16 more.
It answered our last check on 18 October 2026 in 502 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://zerm.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: dev.zerm. Endpoint host: zerm.dev. ARD identifier: urn:air:dev.zerm:mcp:zerm.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.