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.CloudCorpRecords/mailport

NPM · @RENETURCIOS/MAILPORT · 2 COMPONENTS

Gmail messages, threads, labels, drafts and sending, as MCP tools via the Gmail API.

63 Trust /100

Last scanned (4 hours ago)

Scores higher than 31% of npm servers

Category Communication

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 569 tokens (~56/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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; "send_message" implies "send" 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 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 48

    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 5 Nov 2026 · Analysed npm/@reneturcios/mailport@0.1.0

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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~569 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_draft ~94

Create a new Gmail draft message.

NameTypeReqDescription
bccstring–Optional email address to blind-copy in the Bcc header.
bodystringyesThe plain-text body of the draft.
ccstring–Optional email address to copy in the Cc header.
subjectstringyesThe subject line of the draft.
tostringyesThe recipient email address for the To header.

No output schema declared.

No examples provided.

create_label ~33

Create a new label in the user's Gmail mailbox.

NameTypeReqDescription
namestringyesThe name of the new label to create.

No output schema declared.

No examples provided.

get_message ~58

Get a single Gmail message by its ID.

NameTypeReqDescription
formatstring–Optional Gmail message format to return, such as full, minimal, raw, or metadata.
message_idstringyesThe unique identifier of the Gmail message to retrieve.

No output schema declared.

No examples provided.

get_thread ~34

Get a single Gmail thread by its ID.

NameTypeReqDescription
thread_idstringyesThe unique identifier of the Gmail thread to retrieve.

No output schema declared.

No examples provided.

list_labels ~17

List all labels in the user's Gmail mailbox.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_messages ~78

List messages in the user's Gmail mailbox, optionally filtered by a search query or labels.

NameTypeReqDescription
label_idsarray–Optional list of label IDs; only messages carrying all of these labels are returned.
max_resultsnumber–Optional maximum number of messages to return.
querystring–Optional Gmail search query to filter messages by.

No output schema declared.

No examples provided.

list_threads ~53

List threads in the user's Gmail mailbox, optionally filtered by a search query.

NameTypeReqDescription
max_resultsnumber–Optional maximum number of threads to return.
querystring–Optional Gmail search query to filter threads by.

No output schema declared.

No examples provided.

modify_message ~72

Add or remove labels on a Gmail message.

NameTypeReqDescription
add_label_idsarray–Optional list of label IDs to add to the message.
message_idstringyesThe unique identifier of the Gmail message to modify.
remove_label_idsarray–Optional list of label IDs to remove from the message.

No output schema declared.

No examples provided.

send_message ~94

Send a new email message via Gmail.

NameTypeReqDescription
bccstring–Optional email address to blind-copy in the Bcc header.
bodystringyesThe plain-text body of the message.
ccstring–Optional email address to copy in the Cc header.
subjectstringyesThe subject line of the message.
tostringyesThe recipient email address for the To header.

No output schema declared.

No examples provided.

trash_message ~36

Move a Gmail message to the trash.

NameTypeReqDescription
message_idstringyesThe unique identifier of the Gmail message to move to the trash.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/mailport MCP server?

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

npm · @reneturcios/mailport

# add to Claude Code
claude mcp add cloudcorprecords-mailport -- npx -y @reneturcios/mailport
Common questions

What is the io.github.CloudCorpRecords/mailport MCP server?

io.github.CloudCorpRecords/mailport is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/mailport. Gmail messages, threads, labels, drafts and sending, as MCP tools via the Gmail API. This page covers its npm package (@reneturcios/mailport).

Is the io.github.CloudCorpRecords/mailport MCP server safe to use?

io.github.CloudCorpRecords/mailport scores 63 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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.CloudCorpRecords/mailport MCP server expose?

io.github.CloudCorpRecords/mailport exposes 10 tools: list_messages, get_message, list_threads, get_thread, list_labels, and 5 more. Their descriptions and schemas cost roughly 569 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/mailport MCP server still maintained?

io.github.CloudCorpRecords/mailport is still listed as active in the MCP registry. We last reached this channel on 5 November 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.CloudCorpRecords/mailport MCP server under?

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