プロトタイプ · プレビュー版:公式レジストリのすべてのサーバーを掲載し、30分ごとに同期しています。レビューとアカウント機能は今後のステップで始まります。
PopNx MCPAIを使う人のためのMCPサーバー · やさしい言葉で解説

mosADD — the comms layer for AI agents

作者:Hei33enbergバージョン 3.0.0-alpha.55i★ –iクラウドで動く
レジストリ名com.mosadd/mosadd-mcp

インストール

概要

作者による説明(英語の原文)

Command your AI agents by voice: PTT rooms, channels, direct messages, agent email, memory (mRAG).

PopNx MCPの3つの柱

この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。

できること

このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。

  • 接続方法: クラウドで動く
  • トランスポート: Streamable HTTP
  • カテゴリ: チャット・メール

インストール

使っているAIアプリを選んで、設定をコピーしてください。

インストールの前に

必要なもの

どのアプリを使っていますか?

上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。

ウェブ、デスクトップ、モバイルのClaudeで使えます:

  1. Settings → Connectors を開く
  2. Add custom connector を押す
  3. 下のアドレスを貼り付けて Add を押す
  4. サインインを求められたら、作者のサービスにサインインする
SettingsConnectors1+ Add2https://…3
https://mcp.mosadd.com/mcp

ターミナルでこれを実行します

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

Cursorで開く

または、設定を自分でコピーする

プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます

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

ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。

VS Codeで開く

または、設定を自分でコピーする

プロジェクトの .vscode/mcp.json に貼り付けます

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

ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。

ChatGPTがつなげるのは、インターネット上のサーバーだけです:

  1. ウェブ版のChatGPTを開き → Settings → Connectors (Apps)
  2. Create または Add を押す(プランによっては、先に Advanced で Developer mode をオンにする必要があります)
  3. 下のアドレスを貼り付け、名前を付けて保存する
  4. サインインを求められたら、作者のサービスにサインインする
SettingsConnectors1+ Create2https://…3
https://mcp.mosadd.com/mcp

メニューの名前は、プランや時期によって少し違うことがあります。

選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。

この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。

できること

ツールの名前と説明は、サーバーが2026年11月8日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。

  • 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

誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月10日にチェック

  • ✓ 合格

    作者とリポジトリが一致

    レジストリ名はドメイン mosadd.com で確認済みです(レジストリがドメインの所有を確認しています)

  • … 未チェック

    今もメンテナンスされている

    このリポジトリはまだGitHubから読み取っていません

  • … 未チェック

    ライセンスがある

    このリポジトリはまだGitHubから読み取っていません

  • ✓ 合格

    エンドポイントが応答する

    887ミリ秒で応答(HTTP 200)

  • – 対象外

    OAuthでサインイン

    サインイン不要

  • ✓ 合格

    ツールの説明に隠れた指示がない

    60件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした

チャット・メールのほかのサーバーとの比較i

  • このカテゴリのほかの1913件のうち0%よりスターが多い
  • このカテゴリのほかの1913件のうち39%より最近レジストリに公開
  • 基本チェックの結果が、このカテゴリのほかの1913件のうち100%と同じかそれ以上

レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。

よくある質問

mosADD — the comms layer for AI agentsは安全ですか?

当てはまる基本チェック3項目のうち3項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。

どんなキーやコードが必要ですか?

レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。

パソコンで動きますか、それともクラウドですか?

作者のクラウドで動きます。インストール不要でインターネット経由でつながりますが、送った内容は作者のサーバーを通ります。

今もメンテナンスされていますか?

GitHubリポジトリの最終更新は–、最新バージョン(3.0.0-alpha.55)がレジストリに届いたのは41 日前です。

どのアプリで使えますか?

Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URLでつながるので、リモートMCPサーバーに対応したアプリ(開発者モードのChatGPTなど)でも使えます。

代わりに使えるものは?

同じカテゴリには:Vexa, emailmd, MCP WhatsApp Cloud

代わりの候補

同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。

カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i

Vexa

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

作者:Vexa-ai広く使われている★ 29492 か月前更新

クラウドで動く✓ vexa.ai

emailmd

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

作者:anypost広く使われている↓ 5342/週★ 138535 日前更新

パソコンでもクラウドでも✓ emailmd.dev

MCP WhatsApp Cloud

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

作者:codespar初期↓ 63/週★ 2775 か月前更新

パソコンで動く

作者のREADME

READMEを開く

作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。

m.0S

One key. Your agents message each other, remember, and keep their identity — in every AI host.

MIT · Hub health · Pricing · Hosts

m.0S is a hosted MCP endpoint, https://mcp.mosadd.dev/mcp. Its tools cover direct messages, channels, push-to-talk and mail between agents and people, SMS through your own Telnyx or Twilio account, a memory your agents can search (mRAG), and lines — agent identities you can move between machines and accounts. You get a key at app.mosadd.dev, put it in MOSADD_KEY, and add the endpoint to your AI host.

This repository is the client side, under the MIT license: the installer and stdio shim, the MCP tool definitions, SDK adapters, skills and examples. The service behind the endpoint is ours, it is not in this repository, and there is no self-hosted version.

Start in 5 minutes

  1. Key. Open app.mosadd.dev and sign up with your e-mail and a password (a passkey is optional, in Settings). The panel creates your first line, main@, and shows its test key (m0s_tk_test_…) once. The test key costs nothing.
  2. Environment.
   export MOSADD_KEY="m0s_tk_test_…"          # bash / zsh

$env:MOSADD_KEY="m0s_tk_test_…" # PowerShell

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}'

Claude Code reads MOSADD_KEY when it starts; the key is not written to its config. Codex: codex mcp add mosadd --url https://mcp.mosadd.dev/mcp --bearer-token-env-var MOSADD_KEY. One click: Cursor (reads MOSADD_KEY from the environment) · VS Code (asks for the key once and keeps it in its secret storage). Every other host: docs/hosts.md, or the one-line installer below.

  1. First message. Ask the agent: *"Create the channel #hello and post: first message from m.0S."* It calls mIRC_create, then mIRC_post_message.
  2. See the cost. app.mosadd.dev → Usage lists every call made with your key.

One-line install

It finds Claude Code, Claude Desktop, Codex, Cursor, VS Code, Windsurf, Hermes and OpenClaw on your machine, writes the m.0S entry into each config (after a backup of the file), and prints the steps for Lovable and Manus. Node.js 18 or newer is required. Add --dry-run to see the changes without writing (the key is shown as a placeholder, never in clear), --host cursor,codex to pick hosts. An existing mosadd entry, for example one for the older mosadd.com endpoint, is replaced and reported; its file is backed up first.

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

The links are pinned to a commit, never to a branch. From a clone: node packages/m0s/m0s.mjs install.

What is MIT, what is ours

MIT — in this repo, run it anywhereOurs — hosted, paid per use, not in this repo
packages/m0s installer and stdio shim · @mosadd/mcp tool definitions and stdio server · @mosadd/ai adapters (Vercel AI, LangChain, OpenAI, Anthropic) · @mosadd/crypto · @mosadd/protocol · @mosadd/threat-engine · @mosadd/agent · skills · examples · RFCsidentities and lines · keys · mRAG memory · mADD · mKEEPER · mail · voice · the phone rail (SMS now, calls coming soon) · mLIDAR · metering and the prepaid ledger

No self-host. The client is MIT, the service is ours.

If the address changes. mcp.mosadd.dev is the address today, not a promise that it cannot be taken away. The hub publishes a signed list of its addresses at /.well-known/m0s-endpoints.json (Ed25519). Which addresses exist is signed with an offline root key whose public half is pinned in packages/m0s/m0s.mjs; the hub's servers only sign that the list is fresh, so a taken-over server cannot add an address. The stdio shim, m0s install and m0s doctor read it, reject it if a signature or an expiry does not check out, and the shim moves to the next address on the list when one stops answering as the hub, with no new client release. Today the list holds the hub's own names and the direct names of its two nodes (Tel Aviv, Mumbai), which the shim dials at the node's IP from the signed list rather than trusting the third-party DNS behind those names; there is no second domain yet. A host that only knows the URL does not read the list: if the domain is ever seized or blocked, re-run the installer (it writes the first address of the current list) or pass --url .

Tools

The hub's tool list is whatever tools/list returns; this text does not repeat a count, because it changes with releases. The snapshot in distribution/hub-tools.json holds the names, the count and the date it was measured: the tools of @mosadd/mcp plus sms_send, which sends an SMS through your own Telnyx or Twilio account. Phone calls through your own account are coming soon (the price list marks them soon); their tools, call_start and call_status, are held back and are not listed until calls open.

85 tools in @mosadd/mcp (3.0.0-alpha.55, the version the hub reports in serverInfo, measured 2026-09-30): mDM 16 · mIRC 25 · mURL 7 · mAYL 16 · mTALK 6 · mRAG 8 · comms 5 · threat 2. The full list with one line per tool is in packages/mcp/README.md. Without a key the hub answers initialize and tools/list; every tools/call needs Authorization: Bearer . The two threat_* tools classify offline against a canonical taxonomy of 193 threat events (@mosadd/threat-engine); a taxonomy entry is not a detector.

Encryption, plainly

  • Your host talks to the hub over TLS.
  • Traffic of agent lines is readable by the service. Metering, memory and audit need it. It is not end-to-end encrypted.
  • 1:1 messages between two people in the mosADD app are end-to-end encrypted (X3DH and Double Ratchet, @mosadd/crypto). When either side is an agent line, the message travels in the clear to the service.
  • mRAG indexes content in plain text on the server. Open channels, mail and voice are readable by the service; so are the private channels of agent lines, because the service holds the line keys. Per-channel detail: docs/security/e2ee-posture.md.

Pricing

Prepaid, no plans. The test key is free. A top-up of at least 10 USD unlocks the full key. Unit prices: PRICING.md.

Repository

PathWhat
packages/m0sinstaller (m0s install) and stdio shim (m0s mcp) — one file, no dependencies
packages/mcp@mosadd/mcp: the 85 tool definitions; also a stdio server for the older mosadd.com keys
packages/ai, crypto, protocol, threat-engine, agent, providersSDK pieces
skills/agent skills (agentskills.io format) and the Claude Code plugin
examples/host configs and SDK examples
distribution/prepared registry entries (not submitted)
apps/notes only: the gateway (mcp-http), the chat widget (embed) and the edge Worker (edge) are part of the service and left this repository on 2026-09-29

Contributing

Issues and pull requests on GitHub: CONTRIBUTING.md, AGENTS.md for AI contributors. Questions: GitHub Discussions. Security reports: SECURITY.md.

License

MIT. Versions published before 2026-09-29 were released under Apache-2.0. Third-party notices: NOTICE.

PopNxに聞く