Google Workspace MCP VE (HuntsDesk/ve-gws) is an MCP server listed on the M8ven Trust Index. It scores 41 out of 100, grade D. It declares 108 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
41/100

Google Workspace MCP VE

Most Google Workspace MCPs let you read. This one lets you write — 28 authoring tools on top of taylorwilsdon/google_workspace_mcp, including markdown-to-Docs, smart chips, and recursive Drive copy.

→ HuntsDesk/ve-gws· listed on glama

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

HuntsDesk

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.

⏳ This MCP is queued for scoring. Check back in a few minutes.
// key findings
🚨
Reads files from sensitive locations
Touches: credentials, .credentials, credentials
🔐
You'll be asked for 3 credentials: FASTMCP_SERVER_AUTH_GOOGLE_JWT_SIGNING_KEY, GOOGLE_OAUTH_CLIENT_SECRET, GOOGLE_PSE_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
🔐 secretFASTMCP_SERVER_AUTH_GOOGLE_JWT_SIGNING_KEYexport ="$(openssl rand -hex 32)"
configWORKSPACE_MCP_OAUTH_PROXY_STORAGE_BACKENDmemory, disk, or valkey — see [storage backends](#oauth-proxy-storage-backends)
configWORKSPACE_MCP_OAUTH_PROXY_VALKEY_HOSTexport =redis.example.com
configFASTMCP_HOME
configWORKSPACE_MCP_PORTexport =8000
configWORKSPACE_MCP_BASE_URIBase server URI (no port) — default http://localhost
configWORKSPACE_MCP_HOSTBind host — default 0.0.0.0
configWORKSPACE_EXTERNAL_URLExternal URL for reverse proxy setups
🔐 secretGOOGLE_OAUTH_CLIENT_SECRETexport ="..."
configWORKSPACE_MCP_CREDENTIALS_DIR
configGOOGLE_MCP_CREDENTIALS_DIRCredential directory — default ~/.google_workspace_mcp/credentials
configGOOGLE_OAUTH_CLIENT_IDexport ="..."
configMCP_SINGLE_USER_MODE
configMCP_ENABLE_OAUTH21export =true
configGOOGLE_CLIENT_SECRET_PATHCustom path to client_secret.json
🔐 secretGOOGLE_PSE_API_KEYAPI key for Programmable Search Engine
configGOOGLE_PSE_ENGINE_IDSearch Engine ID for PSE
configSESSION_TIME
configGOOGLE_OAUTH_REDIRECT_URIexport ="http://localhost:${WORKSPACE_MCP_PORT}/oauth2callback"
configOAUTHLIB_INSECURE_TRANSPORTrequired* Set to 1 for development — allows http:// redirect
configOAUTHLIB_RELAX_TOKEN_SCOPE
configEXTERNAL_OAUTH21_PROVIDERtrue for external OAuth flow with bearer tokens
configWORKSPACE_MCP_STATELESS_MODEtrue for stateless container-friendly operation
configGOOGLE_SERVICE_ACCOUNT_KEY_FILEPath to service account JSON key file (domain-wide delegation)
configGOOGLE_SERVICE_ACCOUNT_KEY_JSONInline service account JSON key (alternative to file)
configOAUTH_CUSTOM_REDIRECT_URISComma-separated additional redirect URIs
configOAUTH_ALLOWED_ORIGINSComma-separated additional CORS origins
configWORKSPACE_ATTACHMENT_DIRDownloaded attachments dir — default ~/.workspace-mcp/attachments/
configWORKSPACE_MCP_URLRemote MCP endpoint URL for CLI
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

108/108 tools missing one or more hints — start_google_auth (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); func (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_script_projects (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +105 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 handlers catch errors

Only 13/105 tool handlers wrap calls in try/catch (12%)

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.

No access to sensitive paths

Reads sensitive paths: credentials, .credentials, credentials

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

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 5 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/huntsdesk/ve-gws?variant=verified)](https://m8ven.ai/mcp/huntsdesk/ve-gws)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: fae879287943453f22396a6d67c08be05ccb5b52
code hash: d3e9bea6bb145fb67c0c38d443c23e965e077e7dfd7fd0e5008ef36d94ac53ca
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