Gmail MCP Server (suryanandan1/MCP_and_gmail_connection) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 10 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

Gmail MCP Server

Enables Gmail operations such as listing, searching, and reading messages, as well as drafting and sending emails, with OAuth authentication and guarded tool enablement.

→ suryanandan1/MCP_and_gmail_connection· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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

suryanandan1

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 →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

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
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
// tools this server exposes10 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.

health_check

Verify that the MCP server is running and show integration status.

echo_text

Echo non-empty text to verify argument handling and tool responses.

add_numbers

Add two numbers to verify typed numeric tool arguments.

gmail_auth_status

Check local Gmail OAuth credential and token readiness without a network call.

gmail_get_profile

Verify the Gmail API connection and return mailbox totals.

gmail_list_messages

List recent Gmail messages with IDs, sender, subject, date, and snippet.

gmail_search_messages

Search Gmail using Gmail search syntax such as from:, subject:, or is:unread.

gmail_read_message

Read a Gmail message using a message_id returned by list or search.

gmail_create_draft

Create a Gmail draft after explicit enablement in .env.

gmail_send_email

Send an email after explicit enablement in .env.

// quality suggestions

Tool annotations

2/10 tools have annotations

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

All four hints declared on every tool

8/10 tools missing one or more hints — health_check (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); echo_text (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); add_numbers (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +5 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

3/10 tools referenced in tests (30%)

Write tests that reference each tool by name so every tool has at least one test.

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 4 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 Score](https://m8ven.ai/badge/mcp/suryanandan1/mcp_and_gmail_connection)](https://m8ven.ai/mcp/suryanandan1/mcp_and_gmail_connection)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: ed5c374448142507a24d07d99c1a694939d75002
code hash: 527b5a61ebab5195c848f95744bab2efffd24dd6addffea6b9aee1e5e0950307
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