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.

Fluxmail

NPM · FLUXMAIL

Read, search, draft, send, and organize email through Gmail, Outlook, and IMAP/SMTP mailboxes.

Available components

npm · fluxmail 36
0 this week 36 Trust /100

Last scanned (11 hours ago)

Scores higher than 13% of npm servers

Category Communication

Deprecated

This server is marked deprecated in the MCP registry. The registry records this reason: Moved to io.github.fluxmailai/fluxmail.

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
  • Dependency health was assessed across the 285 of 286 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency58
  • Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
  • Cryptographically verified build provenance (signed, bound to churichard/fluxmail). View diagnostics → Pass
  • License check failed: the license (Elastic-2.0) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 1 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 →

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.

  • 5 Nov 26 0
    • CVE-2026-121426 affects this package: high ▼ security
    • CVE-2026-121424 affects this package: high ▼ security
    • CVE-2026-121425 affects this package: high ▼ security
    • GHSA-8c8m-p3m8-cjg8 no longer affects this package ▲ security
    • GHSA-85x2-q946-cp5h no longer affects this package ▲ security
    • GHSA-m943-m63m-w62w no longer affects this package ▲ security
  • 31 Oct 26 0
    • CVE-2026-118773 affects this package: high ▼ security
    • CVE-2026-118764 affects this package: high ▼ security
  • 29 Oct 26 0
    • CVE-2026-118663 affects this package: high ▼ security
  • 28 Oct 26 0
    • CVE-2026-110869 affects this package: high ▼ security
    • CVE-2026-110872 affects this package: high ▼ security
    • CVE-2026-110870 affects this package: high ▼ security
  • 24 Oct 26 −3
    • GHSA-85x2-q946-cp5h affects this package: high ▼ security
    • GHSA-m943-m63m-w62w affects this package: high ▼ security
    • GHSA-8c8m-p3m8-cjg8 affects this package: high ▼ security
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. security
  • 23 Oct 26 0
    • CVE-2026-110871 affects this package: high ▼ security
  • 14 Oct 26 0
    • Stability: 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. security
    • Tool safety: 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. security
    • Schema quality: 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. functional
    • Capabilities: 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. functional
    • Tool coverage: 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. functional
  • 13 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
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/fluxmail@0.12.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo churichard/fluxmail
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/churichard/fluxmail/.github/workflows/publish-release.yml@refs/heads/main
Rekor log index 3091378219
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:d55578dace57d608b8896241d466f152873d599086926cc65b8189ca6d51e04c61f2bc306dfd2cdafc1f478790b506d0edc568b6e505ae08e1a72c8a4

Background: How many MCP packages publish verified provenance →

Vulnerabilities 16 findings
ID CVE Severity Vector Fix available
GHSA-rmxm-3fg6-px4f CVE-2026-118663 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N yes
GHSA-3g3m-2fjr-6pw4 CVE-2026-118773 medium yes
GHSA-g3hv-75wg-m249 CVE-2026-118764 medium yes
GHSA-39m8-27wv-hr27 CVE-2026-110871 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H yes
GHSA-4ffr-jq9g-5ffx CVE-2026-110869 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-4g23-2xm8-66gc CVE-2026-110872 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6vj9-mwq6-2f5v CVE-2026-100701 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-85x2-q946-cp5h CVE-2026-121426 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-8c8m-p3m8-cjg8 CVE-2026-121424 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-8vvx-rff5-p5rq CVE-2026-100702 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-g57g-f23g-4646 CVE-2026-100699 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-g73g-hqqh-jr95 CVE-2026-110870 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-m943-m63m-w62w CVE-2026-121425 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-prgh-xp8r-p3m5 CVE-2026-90776 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-v53p-9fqp-m79j CVE-2026-100700 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
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 285 packages
Packages resolved 285
Deprecated 3
Stale 79
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

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.

Install

How do I install the Fluxmail MCP server?

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

npm · fluxmail

# add to Claude Code
claude mcp add churichard-fluxmail -- npx -y fluxmail
Common questions

What is the Fluxmail MCP server?

Fluxmail is an MCP server listed in the public MCP registry as io.github.churichard/fluxmail. Read, search, draft, send, and organize email through Gmail, Outlook, and IMAP/SMTP mailboxes. This page covers its npm package (fluxmail).

Is the Fluxmail MCP server safe to use?

Fluxmail scores 36 out of 100 on VerifyMCP. We recorded 16 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Fluxmail MCP server still maintained?

Fluxmail is marked deprecated 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 Fluxmail MCP server under?

Fluxmail declares the Elastic-2.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.