Disposable Temp Mail - SnapInbox
Pricing
$1.20 / 1,000 requests
Disposable Temp Mail - SnapInbox
The Disposable Temporary Email API lets you create self-deleting temp emails for quick, secure tasks. Ideal for privacy, spam protection, and one-time sign-ups, it’s an easy way for developers to integrate temp email features.
5.0 (1)
Pricing
$1.20 / 1,000 requests
1
Total users
16
Monthly users
5
Runs succeeded
>99%
Last modified
3 months ago
You can access the Disposable Temp Mail - SnapInbox programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.
{ "mcpServers": { "local-actors-mcp-server": { "command": "npx", "args": [ "-y", "@apify/actors-mcp-server", "--actors", "wilcode/snapinbox-disposable-temp-mail" ], "env": { "APIFY_TOKEN": "<YOUR_API_TOKEN>" } } }}Configure MCP server with Disposable Temp Mail - SnapInbox
You can interact with the MCP server via standard input/output - stdio (as shown above), which is ideal for local integrations and command-line tools such as the Claude desktop client, or you can interact with the server through Server-Sent Events (SSE) to send messages and receive responses, which looks as follows:
{ "mcpServers": { "remote-actors-mcp-server": { "type": "sse", "url": "https://mcp.apify.com/sse?actors=wilcode/snapinbox-disposable-temp-mail", "headers": { "Authorization": "Bearer <YOUR_API_TOKEN>" } } }}You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other supported MCP client of your choice.
If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.
