Disposable Email For Agents

PassAudited by ClawScan on May 10, 2026.

Overview

This is a straightforward disposable-inbox integration, but it relies on an external email/MCP service and an unpinned npx bridge, so use it only for low-sensitivity email.

Before installing, confirm you are comfortable connecting your agent to myagentinbox.com through an npm-based MCP bridge. Use the skill for temporary, low-sensitivity email workflows and avoid receiving confidential messages, credentials, private documents, or important account recovery emails in these inboxes.

Findings (2)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

Installing the MCP configuration may run npm-provided code and connect the agent to an external service, so the behavior depends on the current package and remote endpoint.

Why it was flagged

The setup relies on running an npm-distributed MCP bridge without a pinned version and connects it to a remote MCP endpoint. This is purpose-aligned, but it introduces external package and service provenance considerations.

Skill content
"command": "npx", "args": ["mcp-remote", "https://myagentinbox.com/mcp"]
Recommendation

Verify the MCP bridge and service before use, pin package versions where possible, and only configure this server in environments where a third-party disposable email provider is acceptable.

What this means

Email bodies and attachments received at these disposable addresses may become visible to the external provider and to the agent context when read.

Why it was flagged

The skill routes email contents and attachments through an external MCP-accessible service. This is expected for a disposable inbox tool, but users should understand the data boundary.

Skill content
Read the full content of a specific email message including sender, subject, body, and attachment info... Download an email attachment.
Recommendation

Use disposable inboxes for non-sensitive workflows, avoid personal or confidential information, and consider the disclosed 24-hour inbox lifetime when deciding what to receive there.