Google Jules MCP (samihalawa/google-jules-mcp) is an MCP server listed on the M8ven Trust Index. It scores 56 out of 100, grade D. It declares 13 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
56/100

Google Jules MCP

An MCP server for automating Google Jules that enables seamless integration for task creation, code analysis, and AI-powered development workflows. It supports multiple session modes including Browserbase and cookie-based authentication for both local and cloud environments.

→ samihalawa/google-jules-mcp· 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

samihalawa

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
⚠️
Known vulnerabilities in dependencies: 17 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.
🔐
You'll be asked for 1 credential: BROWSERBASE_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes13 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.

jules_create_task

Create a new task in Google Jules with repository and description

jules_get_task

Get details of a specific Jules task by ID or URL

jules_list_tasks

List all Jules tasks with their status

jules_send_message

Send a message/instruction to Jules in an active task

jules_approve_plan

Approve Jules execution plan for a task

jules_resume_task

Resume a paused Jules task

jules_analyze_code

Analyze code changes and diff in a Jules task

jules_bulk_create_tasks

Create multiple tasks from a list of descriptions and repositories

jules_session_info

Get current session configuration and authentication status

jules_setup_wizard

Interactive session setup wizard for automated Google authentication configuration

jules_get_cookies

Extract current browser cookies for session persistence and backup

jules_set_cookies

Set browser cookies from string or JSON for authentication

jules_screenshot

Take a screenshot of current Jules page for debugging and verification

// known CVEs in dependencies17 high12 low

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

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

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

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

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

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

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

highaxios@1.10.0GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.10.0GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

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.
🔐 secretBROWSERBASE_API_KEYbb_live_g3i-b4WPFh__E3cErKE5rO-jWds # Your API key
configBROWSERBASE_CONTEXT_ID
configBROWSERBASE_PROJECT_IDd718e85f-be7b-497d-9123-b1bbf798f1bb # Your project ID
configBROWSERBASE_SESSION_IDOptional: use existing session
configCHROME_USER_DATA_DIR/Users/yourname/Library/Application Support/Google/Chrome/Default
configCOOKIES_PATH~/.jules-mcp/cookies.json # File to save/load cookies
configGOOGLE_AUTH_COOKIES"session_id=abc123; domain=.google.com; auth_token=xyz789; domain=.google.com"
configHEADLESStrue # Run browser in headless mode
configJULES_DATA_PATH~/.jules-mcp/data.json # Custom data storage path
configSESSION_MODEbrowserbase
configSMITHERY_DEPLOYMENT
configTIMEOUT30000 # Browser timeout in milliseconds
configUSE_EXISTING_SESSION
// quality suggestions

Dependencies

7 dependencies, 1 flagged: playwright

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

13/13 tools missing one or more hints — jules_create_task (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); jules_get_task (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); jules_list_tasks (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +10 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.).

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 17 high severity in production deps — @modelcontextprotocol/sdk@1.13.1 (high), @modelcontextprotocol/sdk@1.13.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 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/samihalawa/google-jules-mcp?variant=verified)](https://m8ven.ai/mcp/samihalawa/google-jules-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 39b4251a78a9d159b77b97063213691557117fd8
code hash: af5ff8b54325c689c5660232b6e7f1be8417a85fa4dd8c1ab46f2cf93550bbcc
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