Moist (TickTockBent/Moist) is an MCP server listed on the M8ven Trust Index. It scores 58 out of 100, grade D. It declares 17 tools. No publisher has claimed this listing.

D
Caution
58/100

Moist

Enables Gmail operations such as reading, sending, searching, and managing emails, threads, labels, and drafts via MCP tools.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

TickTockBent

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: MOIST_CLIENT_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes17 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

moist_auth_status

Check the current authentication status, including email, scopes, and token expiry

moist_auth_logout

Logout and clear stored authentication tokens

moist_create_draft

Create a new email draft

moist_list_drafts

List email drafts with pagination

moist_delete_draft

Delete a draft email

moist_send_draft

Send an existing draft email

moist_list_labels

List all Gmail labels (both system and user-created)

moist_modify_labels

Add or remove labels from a Gmail message

moist_list_messages

Search and list Gmail messages with optional filters and pagination

moist_get_message

Retrieve the full details of a Gmail message including body, headers, and attachment metadata

moist_send_message

Send an email message. Can also reply to an existing message or attach to a thread.

moist_trash_message

Move a Gmail message to the trash

moist_delete_message

Permanently delete a Gmail message. This cannot be undone - use moist_trash_message instead for recoverable deletion.

moist_search

Search Gmail messages using Gmail's full search syntax (from:, to:, subject:, has:attachment, is:unread, label:, etc.)

moist_get_thread

Retrieve a Gmail thread with all its messages

moist_list_threads

List Gmail threads with optional search and filtering

moist_trash_thread

Move an entire Gmail thread to the trash

// known CVEs in dependencies3 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.12.1GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.12.1GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.12.1GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configMOIST_CLIENT_ID"": "your_client_id",
🔐 secretMOIST_CLIENT_SECRET"": "your_client_secret"
configMOIST_REDIRECT_URINo OAuth callback URI (default: http://localhost:3000/oauth/callback)
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

17/17 tools missing one or more hints — moist_auth_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); moist_auth_logout (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); moist_create_draft (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +14 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

13/17 tool handlers declare input schemas (76%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

15/17 tool handlers wrap calls in try/catch (88%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.12.1 (high), @modelcontextprotocol/sdk@1.12.1 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/ticktockbent/moist?variant=verified)](https://m8ven.ai/mcp/ticktockbent/moist)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: db17ee8a1de42aad38388b220a3364b85c2b6e58
code hash: 644362dc1e3534bb2e9ff65f549240cfb7ef7041b81103492a52bcae5bdd67fd
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client