Mcp Server Tempmail

Created By
Selenium399 months ago
An MCP (Model Context Protocol) server for temporary email management using the ChatTempMail API.
Overview

what is Mcp Server Tempmail?

Mcp Server Tempmail is an MCP (Model Context Protocol) server designed for managing temporary email addresses using the ChatTempMail API.

how to use Mcp Server Tempmail?

To use Mcp Server Tempmail, you need to obtain an API key from chat-tempmail.com, configure your MCP client with the API key, and then restart the application.

key features of Mcp Server Tempmail?

  • Get available email domains
  • Create temporary email addresses
  • List and delete emails
  • Retrieve and view email messages
  • Configure webhooks for email notifications

use cases of Mcp Server Tempmail?

  1. Creating temporary email addresses for one-time registrations.
  2. Managing multiple temporary emails for testing purposes.
  3. Receiving and viewing messages sent to temporary emails without revealing personal information.

FAQ from Mcp Server Tempmail?

  • How do I get an API key?

Visit chat-tempmail.com, register, and create an API key in your profile.

  • Can I customize the base URL?

Yes, you can set the TEMPMAIL_BASE_URL environment variable to customize it.

  • What happens to temporary emails after their expiry time?

Temporary emails will automatically expire based on the set expiry time.

Server Config

{
  "mcpServers": {
    "tempmail": {
      "command": "npx",
      "args": [
        "mcp-server-tempmail"
      ],
      "env": {
        "TEMPMAIL_API_KEY": "your-api-key-here",
        "TEMPMAIL_BASE_URL": "https://chat-tempmail.com"
      }
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
Selenium39
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago