Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.mbilalawan926-sys/best-tempmail-mcp

NPM · BEST-TEMPMAIL-MCP · SCANNED SEP 25

Disposable email inboxes for AI agents: create, wait for mail, extract verification codes

Available components

+6 this week 77 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability86
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 504 tokens (~72/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_inbox" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the io.github.mbilalawan926-sys/best-tempmail-mcp server?

io.github.mbilalawan926-sys/best-tempmail-mcp runs locally as an npm package, launched with npx -y best-tempmail-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · best-tempmail-mcp

# add to Claude Code
claude mcp add mbilalawan926-sys-best-tempmail-mcp -- npx -y best-tempmail-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "mbilalawan926-sys-best-tempmail-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "best-tempmail-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mbilalawan926-sys-best-tempmail-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "best-tempmail-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add mbilalawan926-sys-best-tempmail-mcp -- npx -y best-tempmail-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mbilalawan926-sys-best-tempmail-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "best-tempmail-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mbilalawan926-sys-best-tempmail-mcp --command npx --arg -y --arg best-tempmail-mcp
# ~/.hermes/config.yaml
mcp_servers:
  mbilalawan926-sys-best-tempmail-mcp:
    command: "npx"
    args: ["-y", "best-tempmail-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mbilalawan926-sys-best-tempmail-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "best-tempmail-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add mbilalawan926-sys-best-tempmail-mcp -t stdio -c npx -a -y best-tempmail-mcp
// mcp.json
{
  "mcpServers": {
    "mbilalawan926-sys-best-tempmail-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "best-tempmail-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Sept 26 +3
    • Stability: unverified → 0.23 ▲ functional
  • 14 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 13 Sept 26 56

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Sept 2026 · Analysed npm/best-tempmail-mcp@1.0.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 4 packages
Packages resolved 4
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~504 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_inbox ~106

Create a temporary email address that can receive mail. Use this when the user needs an email address for a signup, a trial, or anything they do not want to give a real address to. Returns the address and when it expires.

NameTypeReqDescription
domainstring–Optional domain from list_domains. Random if omitted.
usernamestring–Optional local part, for example 'my-test'. Lowercase letters, digits, dot, underscore and hyphen only. Random if omitted.

No output schema declared.

No examples provided.

delete_inbox ~49

Delete an inbox and everything in it. Inboxes expire on their own, so this is only needed when the user wants it gone immediately.

NameTypeReqDescription
addressstringyesThe inbox address to delete.

No output schema declared.

No examples provided.

get_verification_code ~98

Pull the verification or one-time code out of a message. Use this after wait_for_email when the user needs a code to complete a signup or login. Requires a paid API key. If no code is found with confidence, that is reported rather than guessed, because a wrong code is worse than none.

NameTypeReqDescription
addressstringyesThe inbox address.
message_idstringyesMessage id from wait_for_email or list_messages.

No output schema declared.

No examples provided.

list_domains ~35

List the domains inboxes can be created on. Only needed when the user wants a specific domain; create_inbox picks one automatically.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_messages ~45

List the messages currently in an inbox, newest first. Use this to see what has already arrived, rather than waiting for something new.

NameTypeReqDescription
addressstringyesThe inbox address.

No output schema declared.

No examples provided.

read_message ~71

Read a message's full body and attachment list. Use this when the user wants to see what an email actually says, or when get_verification_code could not find a code.

NameTypeReqDescription
addressstringyesThe inbox address.
message_idstringyesMessage id from wait_for_email or list_messages.

No output schema declared.

No examples provided.

wait_for_email ~100

Wait for the next email to arrive at an inbox, up to 55 seconds. Use this straight after triggering a signup or password reset. Returns the message summary, or reports that nothing arrived. Nothing arriving is not an error: the mail may simply be slow, and calling this again continues waiting.

NameTypeReqDescription
addressstringyesThe inbox address to watch.
timeoutinteger–Seconds to wait. Defaults to 30, maximum 55.

No output schema declared.

No examples provided.

Common questions

What is the io.github.mbilalawan926-sys/best-tempmail-mcp server?

io.github.mbilalawan926-sys/best-tempmail-mcp is listed in the public MCP registry as io.github.mbilalawan926-sys/best-tempmail-mcp. Disposable email inboxes for AI agents: create, wait for mail, extract verification codes. This page covers its npm package (best-tempmail-mcp).

Is the io.github.mbilalawan926-sys/best-tempmail-mcp server safe to use?

io.github.mbilalawan926-sys/best-tempmail-mcp scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.mbilalawan926-sys/best-tempmail-mcp server expose?

io.github.mbilalawan926-sys/best-tempmail-mcp exposes 7 tools: create_inbox, wait_for_email, get_verification_code, list_messages, read_message, and 2 more. Their descriptions and schemas cost roughly 504 tokens of context every time the server is loaded.

Is the io.github.mbilalawan926-sys/best-tempmail-mcp server still maintained?

io.github.mbilalawan926-sys/best-tempmail-mcp is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.mbilalawan926-sys/best-tempmail-mcp server under?

io.github.mbilalawan926-sys/best-tempmail-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.