zas-agent
Related Servers
Alternatives to zas-agent
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables coding agents to keep persistent project memory—rules, decisions, known failures and fixes—and to exchange durable agent-to-agent messages over a channel, including tasks, results, and acknowledgements.Apache 2.0- AlicenseNot gradedqualityAmaintenanceEnables AI agents to create, read, update, list, restore, and share encrypted workspaces and artifacts with version-aware writes, view-only links, and optional public documents.7 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to create, read, update, list, and restore end-to-end encrypted workspaces and artifacts that any other agent or person can access through one shareable link, with version-checked writes and read-only or public sharing variants.7 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to privately store files and create controlled share links with expiry, open limits, recipient restrictions, approval gates, revocation, and access logging.MIT
- AlicenseNot gradedqualityAmaintenanceLets agents create, read, update, list, and restore shared encrypted workspaces and artifacts, exchanging a single link that both people and other AI agents can open and edit. Content is encrypted client-side with version-checked writes, so concurrent writers can't silently clobber each other and links can be shared as read-only or editable.7 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables secure credential storage for AI agents by encrypting secrets and providing agent-invisible references, ensuring sensitive data never leaks to the model.MIT
TDQS
Scored across 13 tools
Most tools target distinct actions: pairing/status, sending notes/files, Directo transfers, receiving, job tracking, and item editing are separable. Some boundaries are subtle—especially zas_send_file vs zas_send_direct and the two fallback tools vs their primary operations—but descriptions clarify channel mode and failure context.
All tools use a consistent zas_ prefix and snake_case naming. Most follow a verb_noun pattern, with minor deviations such as zas_status and zas_jobs being noun-like, but the convention remains readable and predictable.
Thirteen tools is well within the appropriate range for this domain, covering pairing, sending, receiving, job tracking, and item lifecycle. The fallback and direct-transfer variants each earn their place by handling distinct operational modes.
The surface covers core lifecycle operations: pair/status, send note/file, direct send/receive, fallbacks, list/get/edit/replace items, and jobs. A notable gap is item deletion or unpairing, though agents can work around these for most workflows.