No user-submitted related servers found.
Scored across 6 tools
Each tool targets a distinct operation — write, fetch bytes, block-for-new, status-check, id-survey, reply-traversal — and the descriptions aggressively cross-reference each other to prevent confusion (e.g., 'Ask exists when...', 'ask get_relay when you want the record'). The only potential overlap, exists versus get_relay's refusal states, is explicitly resolved in both descriptions.
Five of six tools follow a consistent verb_noun snake_case pattern: append_relay, get_relay, wait_for_relay, list_relays, list_replies. The lone exception is 'exists', a bare verb with no noun object, which breaks the otherwise uniform convention.
Six tools is well-scoped for an append-only relay: exactly one tool per core operation with no redundancy. Each tool earns its place, from the single write path to the wait primitive that enables multi-exchange turns.
The surface fully covers the append-only relay domain: deposit, fetch exact bytes, status check, full id survey with paging via 'after', blocking wait for new arrivals, and one-level reply traversal with a documented path to deeper traversal. Update and delete are intentionally absent by design (records cannot be overwritten or removed), so there are no dead ends.