Datovka Multibox
Related Servers
Alternatives to Datovka Multibox
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for accessing Czech datové schránky (ISDS) with legal semantics. Enables AI agents to safely read, send, and archive messages while respecting delivery triggers and deadlines.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables a single account holder to search and read mail, save drafts, send plain-text messages, change read flags, and receive signed new-mail webhooks, with encrypted state and cross-platform self-hosting.1MIT
- AlicenseNot gradedqualityBmaintenanceRead, send and organize IMAP/SMTP email, and read and arrange Google and CalDAV calendars, through a local policy daemon. Sends to addresses off the allowlist are held as drafts, passwords stay in an encrypted vault, and every call goes to an audit log.MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server exposing the Czech ISDS Data Box system (Datové schránky) as tools, built on fastmcp and python3-datovka.1LGPL 3.0
- FlicenseNot gradedqualityCmaintenanceProvides secure, draft-first IMAP/SMTP access to a GMX business mailbox over Streamable HTTP, letting users list folders, read, search and download attachments, and create, update or delete drafts and replies. Sending is never arbitrary: it requires an explicit user-approved send of a previously reviewed draft, and email content is always treated as untrusted data.-
- AlicenseNot gradedqualityCmaintenanceEnables searching, reading, sending, replying to, forwarding, and organizing email across multiple SMTP/IMAP accounts.MIT
TDQS
Scored across 8 tools
The read path (list_boxes, list_received, list_sent, read_message) and the write path (prepare_message, get_draft, send_draft) are cleanly separated, and the immutability/approval semantics are spelled out. The only real overlap is datovka_search_box versus datovka_list_boxes, which an agent could confuse since both concern data boxes; the descriptions disambiguate but require careful reading.
Every tool uses the datovka_ prefix with a consistent snake_case verb_noun pattern (list_received, read_message, prepare_message, send_draft, get_draft). The verb choices map predictably to action semantics: list for collections, get for a single known artifact, read for content retrieval.
Eight tools is well-scoped for a mail/data-box client, with each tool covering a distinct step in the receive-compose-approve-send workflow. Nothing looks redundant, and the split between prepare_message, get_draft, and send_draft is justified by the immutable-draft design.
Core lifecycle is covered for received mail and for outgoing drafts, but the surface has notable gaps: sent messages can be listed yet never read in full (read_message is receive-only), there is no way to delete or discard a draft, and no message-level search or attachment enumeration beyond reading a message. Approval being outside MCP is a deliberate design choice rather than a gap, but the read side of outbound mail remains a dead end.