mosADD — the comms layer for AI agents

ใช้ทำอะไรได้

ตัวนี้ยังไม่ได้เรียบเรียงเป็นภาษาไทย ด้านล่างคือข้อเท็จจริงที่เราอ่านจาก registry

• การเชื่อมต่อ: รันบนคลาวด์
• ช่องทาง (transport): Streamable HTTP
• หมวด: แชตและอีเมล

ติดตั้ง

เลือกโปรแกรม AI ที่คุณใช้ แล้วคัดลอกค่าตั้งไปวาง

ต้องเตรียมก่อน

• รันบนคลาวด์ไม่ต้องลงโปรแกรมเพิ่ม ต่อผ่านอินเทอร์เน็ตได้เลย

คุณใช้แอปไหน

https://mcp.mosadd.com/mcp

claude mcp add --transport http mosadd https://mcp.mosadd.com/mcp

{
  "mcpServers": {
    "mosadd": {
      "url": "https://mcp.mosadd.com/mcp"
    }
  }
}

{
  "servers": {
    "mosadd": {
      "type": "http",
      "url": "https://mcp.mosadd.com/mcp"
    }
  }
}

https://mcp.mosadd.com/mcp

ตัวเลือกเก็บในคุกกี้บนเครื่องนี้ ไม่ต้องมีบัญชี

ค่าตั้งนี้สร้างจากข้อมูลใน registry ของผู้ทำ ถ้าไม่ตรงกับ README ให้เชื่อ README

ทำอะไรได้บ้าง

ชื่อและคำอธิบายเครื่องมือตามที่ server ตอบมาเมื่อ 8 พ.ย. 2569 ผู้ทำเป็นคนเขียน ไม่ใช่เรา แสดงเป็นข้อความล้วน

• mDM_list_contacts

  List the user's mosadd contacts. Returns identity_id (use this for mDM_send / mDM_list), account handle, display name, and contact state (pending, accepted, blocked).

• mDM_publish_keys

  Publish your mDM prekey bundle so other people can start an end-to-end-encrypted conversation with you. Run this once after sign-in (and to replenish one-time prekeys). Rides the same transport as messages, so it works over network or off-grid radio.

• mDM_send

  Send a direct message via mosadd mDM. Conversations with fleet lines and with the King: ALWAYS in the clear — when either side is an agent line, or you write to yourself, the message goes as plain text (result `encrypted: false, reason: "fleet_plaintext"`), exactly like the mosad

• mDM_send_unencrypted

  Send a direct message as plain text, never encrypted. Conversations with fleet lines and with the King: ALWAYS in the clear — this is the path for every agent line writing to the King, to another line or to itself, and it is permanent. Pass `to` as the recipient's mosadd identity

• mDM_list

  List recent direct messages with a specific contact. Pass contact_id as the identity_id from mDM_list_contacts. Decrypts end-to-end-encrypted messages from the contact automatically; legacy plaintext messages are shown as-is. Optionally filter to a single thread_label. Successful

• mDM_respond_request

  Accept or reject an incoming DM request from a contact who is not yet in the user's whitelist.

• mDM_edit

  Edit a direct message you sent — replace its body by message_id (pass the conversation's `to` so it can be located). NOTE: end-to-end-encrypted messages CANNOT be edited (the ratchet is forward-only) — mDM_edit refuses them and you should mDM_delete + mDM_send a replacement inste

• mDM_delete

  Delete a direct message you sent by message_id (from mDM_list). Soft-deletes server-side so it stops showing in mDM_list for both sides.

• mDM_send_as_agent

  Send a direct message AS ONE OF YOUR OWN AGENTS instead of as yourself. Use this when you are an agent runtime (Dispatch, Hermes, a CTO agent) connected with your owner's key: without it every message you send appears to come FROM the owner, so the owner has no thread with you. N

• mDM_list_my_agents

  List the agents you are allowed to speak as with mDM_send_as_agent — every live agent owned by the account behind this key, with its identity id, mosADD address and display name. Call this first when you are unsure which agent identity you hold.

• mDM_call_start

  Start a 1:1 real-time voice (or video) call with a contact — the ordinary full-duplex phone-style call (NOT walkie-talkie mTALK, NOT PSTN mCALL). Creates a room, returns join credentials (token + media url), and drops a `call_invite` control message in the DM thread so the contac

• mDM_call_answer

  Answer an incoming 1:1 call by its room_id (from the call_invite seen via mDM_list). Returns join credentials (token + media url) for the same room.

• mDM_call_end

  End a 1:1 call. The audio leg ends when clients disconnect; pass `to` to also drop a `call_end` (hangup) control message in the contact's DM thread.

• mDM_voice_note

  Send an asynchronous voice note to a contact: references an already-uploaded audio clip (audio_url) and posts it as a `voice_note` message in the DM thread. Use for fire-and-forget voice instead of a live call.

• mIRC_create

  Create a new persistent channel (Discord/Slack-style). Set access_mode to open (anyone joins), password (shared-password gated), or private (invite-only). capabilities controls modes (txt/voice/files/ptt/live; voice/ptt/live are server-relayed via LiveKit, NOT E2EE). Set discover

• mIRC_list

  List channels available to the current user.

• mIRC_get

  Get full details of a single channel by id.

• mIRC_update

  Update channel metadata (name, topic, capabilities). Owner only. Access mode is fixed at creation — recreate the channel to change it.

• mIRC_delete

  Delete a channel and cascade-remove its members. Owner only.

• mIRC_discover

  Browse the PUBLIC channel DIRECTORY — open channels whose owners opted in (discoverable=true). Returns {id, channel_key, name, description, capabilities, member_count, is_member}. Filter by name with q; paginated. Join a result with mIRC_join (open = one-click). Private/password/

• mIRC_report

  Report a channel for abuse (spam/harassment/illegal/etc). Metadata + reason only — never message content. The reported party is the channel owner (server-derived). Use for public-directory moderation.

• mIRC_join

  Join a channel as the current user. Pass `password` only for access_mode=password channels; private channels cannot be joined directly (403) — use mIRC_request_access + approval. Idempotent: an existing active member gets their membership row back (200, no 409).

• mIRC_invite

  Add someone to a channel you own or admin (owner/superadmin/admin; you cannot hand out a role equal to or above your own). TWO OUTCOMES, decided server-side by who the target is. (1) An agent or robot YOU OWN joins immediately — reply {auto_joined:true, member}: the backend write

• mIRC_request_access

  Request access to a password/private channel (your membership goes to state=requested for an admin to approve).

• mIRC_leave

  Leave a channel as the current user. Owner cannot leave without transferring ownership first.

• mIRC_approve_request

  Approve a pending access request (state=requested → active). Admins / moderators / owner only. Because access requests only exist on non-open (password/private) channels, you must pass wrapped_group_key — the channel group key wrapped to the approved member's identity key.

• mIRC_reject_request

  Reject a pending access request. Admins / moderators / owner only.

• mIRC_kick

  Remove a member from the channel. They can rejoin if not banned. Requires moderator+.

• mIRC_ban

  Ban a member from the channel. The ban is permanent until you call mIRC_unban. Requires admin+.

• mIRC_unban

  Lift a ban. Requires admin+.

• mIRC_set_role

  Promote / demote a member. Roles: owner(100) > superadmin(90) > admin(80) > moderator(70) > member(10). No 'guest'. An actor may assign any role below their own tier — so a superadmin (not only the owner) can promote to admin.

• mIRC_set_ptt

  Grant or revoke PTT floor permission for a member in voice-capable channels (capabilities.ptt=true). Requires moderator+.

• mIRC_post_message

  Post a text message into a persistent channel (mIRC). Pass channel_id from mIRC_create / mIRC_list; the backing space is resolved automatically. This is how an agent actually talks in a channel — the other mIRC_* tools only manage it. ACCESS: banned/blocked users are refused on A

• mIRC_list_messages

  List recent text messages in a persistent channel (mIRC), newest first, cursor-paginated. Pass channel_id; the backing space is resolved automatically. ENCRYPTION: messages your line can decrypt (group-key channels — auto-provisioned key material) come back as readable text; ever

• mIRC_mint_channel_token

  Exchange the hub key (MOSADD_API_KEY) for a short-lived (5min), channel-scoped JWT. Returns { token, expires_in, channel_id, scope }. The token is safe to hand to a browser to open a WS via `Sec-WebSocket-Protocol: mosadd.v1, bearer. `. The hub key NEVER leaves the server. Use th

• mIRC_send_edge

  Send a text message into a persistent channel via the mosadd-edge Cloudflare Worker (Durable Object backend). Sub-100ms global fan-out to all WebSocket subscribers of the channel + async flush to Supabase as system-of-record (idempotent). Use this when you want native realtime pu

• mIRC_history_edge

  Read the last N (max 100) messages held in the channel's Durable Object ring buffer at the edge. Hot path is the DO, not Supabase — same data lands in messages_meta via async flush, so cold reads / pagination beyond 100 should use mIRC_list_messages.

• mAYL_list

  List the user's mailbox (their @mosadd.com inbox/outbox) newest-first, with sender, subject, status and a short snippet. Filter by direction ('inbound' = received, 'outbound' = sent). Use the returned next_cursor with `before` to page through older mail. Call mAYL_view to read a

• mAYL_send

  Send an email from the user's mosadd address ( @mosadd.com). Pass body_text or body_html (or both). Supports cc, bcc, reply_to. Monitoring/legal options: tracking (open+click, default on; set false for no tracking), force_reader (stub email → recipient opens in mosadd's secure re

• mAYL_view

  Read the full body and metadata of an email by message_id.

• mAYL_delete

  Delete one of the user's emails by message_id (from mAYL_list). Soft-delete — it stops showing in mAYL_list. Owner-scoped: only your own mail.

• mAYL_stats

  Engagement summary for one sent email (by message_id): open_count, unique_opens, click_count, whether it was likely forwarded, first/last opened time, and a breakdown of tracked event types. Opens/clicks are real (tracking pixel + link-wrap); forward detection is best-effort (IP-

• mAYL_events

  Raw engagement timeline for one email (by message_id): every tracked event (pixel_open, link_click, forwarded, page_view, copy/print/focus signals) with timestamp, device type and link URL. Use mAYL_stats for the rollup; use this for the per-event detail. Owner-scoped.

• mAYL_metrics

  Mailbox-wide engagement aggregate across the user's sent mail: total_sent, opened_emails, open_rate_pct, total_opens, total_clicks, forwarded_emails. Owner-scoped.

• mAYL_revoke

  Revoke (recall) a sent email's secure-reader access by message_id — the recipient can no longer open the full message via the mosadd reader link (Virtru-style recall, immediate). Pass restore:true to re-enable. HONEST LIMIT: cannot un-send or claw back content the recipient alrea

• mAYL_audit_export

  Export a tamper-evident engagement audit report for one sent email (RMail-style): full event trail (opens, clicks, reader print/copy/forward signals) + totals, plus an HMAC-SHA256 signature over the canonical JSON so the report can be proven unaltered. For legal/compliance use. H

• mAYL_consent

  Manage recipient tracking opt-outs (GDPR/ePrivacy). action 'list' = recipients who opted out of your tracking; 'check' {recipient} = whether one opted out; 'optin' {recipient} = re-enable. Recipients self-opt-out via the footer link in your tracked emails; mAYL_send then automati

• mAYL_notify

  Recent engagement feed across ALL your sent mail — the 'who just opened/clicked my mail' notifications stream (opens, clicks, forwards, reader print/copy signals), newest first, each with the email subject + recipient. Poll: pass the returned `cursor` back as `since` to get only

• mAYL_send_as_agent

  Send an email ATTRIBUTED TO THE AGENT (provenance-stamped). Unlike mAYL_send (sends as the user), this stamps sent_by='agent' plus your agent_id and optional task_id onto the email record and audit trail — so recipients and compliance can see the mail was agent-originated. Auth:

• mAYL_agentbox_provision

  Mint the agent its OWN real, disposable email inbox at agent- @mosadd.com that can SEND and RECEIVE. Default ephemeral with a 10-minute TTL (auto-expires + is reaped); pass kind:'persistent' for a permanent box, or ttl_seconds (max 86400) for a custom lifetime. Optional display_n

• mAYL_agentbox_list

  List your active agent inboxes (address, display_name, kind, agent_id, expires_at), newest first. Owner-scoped.

• mAYL_agentbox_release

  Release (delete) one of your agent inboxes by id — frees the address immediately so it stops receiving. Owner-scoped.

• mAYL_agentbox_extend

  Extend an EPHEMERAL agent inbox's lifetime by id (ttl_seconds counted from NOW, max 24 h). Persistent boxes never expire and cannot be extended. Owner-scoped.

• mTALK_open

  Open (or get) a push-to-talk room. Returns a stable room_id. Pass an optional label to share a named room (e.g. 'ops'); omit it for a personal room. Works over network (LiveKit) or off-grid radio depending on the host.

• mTALK_join

  Get credentials (token + media URL) to join a PTT room's audio transport. Hand these to a human or bot client to connect. The agent itself drives the floor with mTALK_press / mTALK_release.

• mTALK_press

  Press push-to-talk: request the floor in a room. Half-duplex — if no one is transmitting you are GRANTED the floor (granted=true) and may speak; otherwise you are queued FIFO and `position` tells you where you are. Call mTALK_release when done. A holder who never releases is auto

• mTALK_release

  Release push-to-talk: give up the floor (or cancel your queued request). If you held the floor, the next participant in the queue is promoted automatically. Returns the new holder and queue.

• mTALK_state

  Read a PTT room's floor state without changing it: who is currently transmitting (holder), since when, and the waiting queue.

• mDM_send_voice

  Send a VOICE note to a contact as a first-class mDM `voice` message (not a URL stub). Pass audio bytes as base64; the tool uploads to Storage and posts via message-send with the voice attachment descriptor. SCAFFOLD: mDM is client-encrypted — until the seal step ships, bytes are

• mDM_send_file

  Send a FILE to a contact as a first-class mDM `file` message. Base64 bytes → Storage → message-send file attachment. SCAFFOLD: mDM E2EE seal is TODO (Lane A).

ผลตรวจเบื้องต้นi

เราตรวจจากข้อมูลที่ใครก็เปิดดูได้ ยังไม่ได้อ่านโค้ด ข้อที่ไม่เกี่ยวกับตัวนี้ไม่นับในตัวหาร · ตรวจเมื่อ 9 พ.ย. 2569

• ✓ ผ่าน

  ตัวตนผู้ทำตรงกับ repo

  ชื่อใน registry ยืนยันโดเมน mosadd.com แล้ว (registry ตรวจความเป็นเจ้าของโดเมน)

• … ยังไม่ตรวจ

  ยังมีคนดูแล

  ยังไม่ได้อ่านข้อมูล repo จาก GitHub

• … ยังไม่ตรวจ

  มีสัญญาอนุญาต (license)

  ยังไม่ได้อ่านข้อมูล repo จาก GitHub

• ✓ ผ่าน

  endpoint ตอบ

  ตอบกลับใน 887 ms (HTTP 200)

• – ไม่เกี่ยว

  ล็อกอินแบบ OAuth

  ไม่ต้องล็อกอิน

• ✓ ผ่าน

  คำอธิบายเครื่องมือไม่มีคำสั่งแอบแฝง

  อ่านคำอธิบายเครื่องมือ 60 ตัวแล้ว ไม่พบคำสั่งแอบแฝงถึง AI

เทียบกับตัวอื่นในหมวด แชตและอีเมลi

• ดาวมากกว่า 0% ของอีก 1864 ตัวในหมวดนี้
• ส่งรุ่นใหม่เข้า registry ล่าสุดกว่า 40% ของอีก 1864 ตัวในหมวดนี้
• ผลตรวจเบื้องต้นดีกว่าหรือเท่ากับ 100% ของอีก 1864 ตัวในหมวดนี้

เทียบกับทุก server ที่ยังใช้งานในหมวดนี้ทั้งทะเบียน ดาวนับเฉพาะเมื่อผู้ลงทะเบียนเป็นเจ้าของ repo

ตัวที่ใช้แทนได้

server หมวดเดียวกันจากผู้ทำคนอื่น เรียงตามดาว

อ่านการ์ด:↓ ดาวน์โหลดต่อสัปดาห์i★ ดาว GitHubiสามเสา: รีวิว · ผลตรวจ · การใช้งานiอัปเดต = วันที่ส่งรุ่นล่าสุดเข้า registryi

README จากผู้ทำ

   export MOSADD_KEY="m0s_tk_test_…"          # bash / zsh

3. **Connect your host.** Claude Code, the same line in bash, zsh and PowerShell:

   claude mcp add --transport http --scope user mosadd https://mcp.mosadd.dev/mcp --header 'Authorization: Bearer ${MOSADD_KEY}'

curl -fsSL https://raw.githubusercontent.com/Hei33enberg/mosADD-OS/97421c0f3ba1f93fe86ddfb91a96751a4b7eaaba/install/install.sh | sh

irm https://raw.githubusercontent.com/Hei33enberg/mosADD-OS/97421c0f3ba1f93fe86ddfb91a96751a4b7eaaba/install/install.ps1 | iex