MCP Uptime
← MCP Reliability Index  /  Web & Scraping
Z

zerm

dev.zerm/zerm
Utility MCP server for AI agents: durable memory, scheduled callbacks, live lookups, fixtures.
healthy
status
21
tools exposed
1017ms
connect latency
a35534b8b728
schema fingerprint

Tools (21)

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
Delete a key from your namespace.
kv_list
List keys in your namespace, optionally filtered by prefix. Use it to discover what earlier runs saved before deciding what to restore. Returns at most 100 keys.
timer_verify_origin
One-time consent handshake before timers can deliver to an origin. POSTs {type:"zerm.origin_verification", token} to the given URL; the endpoint must respond 2xx with the token echoed in the body. Verification covers the whole origin (scheme+host).
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. The target origin must first pass timer_verify_origin. Delay 10s-30d, payload max 8192 bytes, 3 delivery attempt
timer_cancel
Cancel a pending timer by id.
timer_status
Check a timer: status (pending|delivering|delivered|failed|cancelled), attempts, last error.
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. Note: "unregistered" domains can still be registry-reserved or premium-priced; only a registrar checkout is final. Need another registry or platfo
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 DST transition dates for that year (exact to the hour), and the timezone abbreviation. Use this to understand DST behavior before scheduling.
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

Endpoint

https://zerm.dev/mcp
Category: Web & Scraping · Last checked: 2026-07-30T13:44:27Z

Monitor your own MCP server

Get alerted the moment yours goes down, a tool schema drifts, or an upstream silently breaks.

Get early access
How we measure →
What this means. This server responded to the MCP handshake and listed its tools without authentication. The schema fingerprint lets us flag if tool signatures silently change (schema drift) between checks.