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.

mailsocket

PYPI · MAILSOCKET-MCP · 2 COMPONENTS · SCANNED OCT 2

Email inboxes for AI agents: create an inbox, then block until the OTP or magic link arrives.

Available components

remote · mcp.mailsocket.app 28 pypi · mailsocket-mcp 40
40 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
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the mailsocket MCP server?

mailsocket runs locally as a PyPI package, launched with uvx mailsocket-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mailsocket-mcp

# add to Claude Code
claude mcp add app-mailsocket-mailsocket-mcp -- uvx mailsocket-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "app-mailsocket-mailsocket-mcp": {
      "command": "uvx",
      "args": [
        "mailsocket-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "app-mailsocket-mailsocket-mcp": {
      "command": "uvx",
      "args": [
        "mailsocket-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add app-mailsocket-mailsocket-mcp -- uvx mailsocket-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-mailsocket-mailsocket-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "mailsocket-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add app-mailsocket-mailsocket-mcp --command uvx --arg mailsocket-mcp
# ~/.hermes/config.yaml
mcp_servers:
  app-mailsocket-mailsocket-mcp:
    command: "uvx"
    args: ["mailsocket-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "app-mailsocket-mailsocket-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mailsocket-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add app-mailsocket-mailsocket-mcp -t stdio -c uvx -a mailsocket-mcp
// mcp.json
{
  "mcpServers": {
    "app-mailsocket-mailsocket-mcp": {
      "command": "uvx",
      "args": [
        "mailsocket-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.

  • 2 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
    • Security disclosure: fail → pass ▲ functional
  • 1 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Security disclosure: unverified → fail ▼ functional
    • Package version: 0.2.2 → 0.2.3 functional
  • 30 Sept 26 +20
    • Malware scan: unverified → pass ▲ security
    • Source repository: fail → pass ▲ security
    • Package version: 0.1.1 → 0.2.2 functional
    • Package version: 0.1.1 → 0.2.1 functional
    • Package version: 0.1.1 → 0.2.0 functional
  • 29 Sept 26 19

    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 2 Oct 2026 · Analysed pypi/mailsocket-mcp@0.2.3

Provenance No attestation

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

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 29 packages
Packages resolved 29
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the mailsocket MCP server?

mailsocket is an MCP server listed in the public MCP registry as app.mailsocket/mailsocket-mcp. Email inboxes for AI agents: create an inbox, then block until the OTP or magic link arrives. This page covers its PyPI package (mailsocket-mcp).

Is the mailsocket MCP server safe to use?

mailsocket scores 40 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 2 October 2026. 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.

Is the mailsocket MCP server still maintained?

mailsocket is still listed as active in the MCP registry. We last reached this channel on 2 October 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 mailsocket MCP server under?

mailsocket declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.