Connect-MCP

zerm

dev.zerm/zerm · v0.3.3

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

MCPremoteno credentialsEmail

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 24 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 80/100

What it does: 24 tools · 12 read, 12 write (incl. delete/pay) · Email

Test call tz_convert: failed — tool error: {"error":"datetime is required: an ISO 8601 datetime such as \"2025-03-09T02:30:00\" (aliases: timestamp, time)"} (907 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: 0
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://zerm.dev/mcp

Tools

24 tools listed at last check
  • 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.

Badge

Connect-MCP badge for dev.zerm/zerm

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/dev.zerm/zerm.svg)](https://clawy.uk/mcp/s/dev.zerm/zerm)

Website