What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: automate business workflows.Similar tools
Listed for the same task: automate business workflowsReviews
No review yet. Used zerm? Be the first to help others choose.What it does
zerm is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to one capability: api integration. That makes it a candidate for tasks such as automate business workflows or build an internal tool.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2d ago (live check)Hosted endpoint
https://zerm.dev/mcpstreamable-http
In Claude Code: claude mcp add --transport http zerm https://zerm.dev/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"zerm": {
"url": "https://zerm.dev/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 2d agoONLINE zerm answered an MCP connection on 15 Nov 2026 and introduced itself as zerm 0.3.4 (MCP protocol 2025-06-18).
24 tools offered to AI assistants
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 kkv_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 TTLkv_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, netimer_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 POSTtimer_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 titimer_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 thatemail_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 addressurl_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 vericron_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
Show 12 more
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 sfixture_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, ndjtz_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 thattz_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 instantdns_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, domainrequest_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 afterlock_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 oninbox_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 isinbox_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 consuinbox_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.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Version | 0.3.4 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Hosted endpoint | https://zerm.dev/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Website | https://zerm.dev | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
- VERSION02 Nov 20260.3.3 → 0.3.4
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is zerm still online?
Free alerts · no account▲ 0Do you run zerm? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about zerm
How do I connect zerm?
Use the hosted endpoint https://zerm.dev/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does zerm offer?
When Electra Index connected on 15 Nov 2026, it listed 24 tools: kv_set, kv_get, kv_delete, kv_list, timer_verify_origin, timer_schedule, timer_cancel, timer_status and more. The full list is in "Live check" above.
Is zerm online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 2d ago.
What can I use zerm for?
Based on its description, it is most relevant to: automate business workflows, build an internal tool, integrate two APIs, build data pipelines.