Google Drive MCP Server (jrubiosainz/foundry-gdrive-mcp-agent) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 3 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
7 days ago

Google Drive MCP Server

Self-hosted MCP server enabling Foundry agents to search, list, and read Google Drive files via the Drive API with server-side OAuth authentication.

→ jrubiosainz/foundry-gdrive-mcp-agent· 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

⚡ 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

jrubiosainz

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
🚨
Secret credentials may flow to a network call
3 flows detected: GOOGLE_TOKEN_URI, GOOGLE_OAUTH_CLIENT_SECRETS. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 3 credentials: MCP_SHARED_SECRET, GOOGLE_CLIENT_SECRET, GOOGLE_REFRESH_TOKEN
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.
🔐 secretMCP_SHARED_SECRETSecret the URL ?key= must match
configGOOGLE_TOKEN_URI
configMAX_CONTENT_CHARSTruncate file content length
configGOOGLE_CLIENT_IDOAuth refresh token (GOOGLE_CLIENT_ID/SECRET/REFRESH_TOKEN app settings)
🔐 secretGOOGLE_CLIENT_SECRETFrom credentials.json (set by script)
🔐 secretGOOGLE_REFRESH_TOKENFrom token.json (set by script)
configMCP_SERVER_URLhttps://<app>.azurewebsites.net/mcp?key=<secret>
configGOOGLE_OAUTH_CLIENT_SECRETS
configGOOGLE_TOKEN_PATH
configGOOGLE_OAUTH_PORT
configPROJECT_ENDPOINTFoundry project endpoint.
configMODEL_DEPLOYMENT_NAMEe.g. gpt-4o-mini.
configMCP_ALLOWED_TOOLSRestrict them with if you want (e.g. search_files,get_file_content).
configMCP_CONNECTOR_ID
configMCP_REQUIRE_APPROVALnever (service runs tools) or always (app auto-approves + logs)
configAGENT_NAMEAgent name
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

3/3 tools missing one or more hints — search_files (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_files (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_file_content (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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.

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets not logged

10 secret values sent to print

Redact or omit secret values from log output.

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/jrubiosainz/foundry-gdrive-mcp-agent)](https://m8ven.ai/mcp/jrubiosainz/foundry-gdrive-mcp-agent)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 982aa0e2ab4deb896c5e0f0446e9e4c20c541185
code hash: 6321a03d4699873c1d495ff19e304c7973b1448e9cb178a6a64d050d596fc996
verified: 9/6/2026, 7:23:13 AM
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