F
Warning
37/100
14 days ago

colab-cli-mcp

Enables MCP clients to execute Python code on Google Colab GPU/TPU runtimes via the official Colab CLI, with session, file, and package management capabilities.

Warning. Serious findings were identified. Review the full report before connecting. 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

animationsaver

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

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
⚠️
Tool annotations don’t match behaviour
1 read-only tool performs write/delete/exec — read_remote_file (line 173: local.unlink(missing_ok=True))
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: COLAB_CLI_MCP_OAUTH_CLIENT_SECRET
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.
configCOLAB_CLI_MCP_TRANSPORT
configCOLAB_CLI_MCP_HOST
configCOLAB_CLI_MCP_PORT
configCOLAB_CLI_MCP_PATH
configCOLAB_CLI_MCP_AUTH
configCOLAB_CLI_MCP_BASE_URLexport =https://colab-mcp.example.com
configCOLAB_CLI_MCP_OAUTH_CLIENT_IDexport =...
🔐 secretCOLAB_CLI_MCP_OAUTH_CLIENT_SECRETexport =...
configCOLAB_CLI_MCP_OAUTH_REDIRECT_PATH
configCOLAB_CLI_MCP_OAUTH_NO_CONSENT
configCOLAB_CLI_MCP_OIDC_CONFIG_URL
configCOLAB_CLI_MCP_EXECUTABLE
configCOLAB_CLI_MCP_COLAB_AUTH
configCOLAB_CLI_MCP_COLAB_OAUTH_CONFIG
configCOLAB_CLI_MCP_COLAB_STATE
configCOLAB_CLI_MCP_WORKSPACE
// quality suggestions

Tool annotations

10/17 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

17/17 tools missing one or more hints — list_sessions (missing: destructiveHint, idempotentHint, openWorldHint); session_status (missing: destructiveHint, idempotentHint, openWorldHint); create_session (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 annotations match behaviour

1 read-only tool performs write/delete/exec — read_remote_file (line 173: local.unlink(missing_ok=True))

Either remove the readOnlyHint:true annotation, or remove the write/delete call from the tool handler.

Destructive tools are labelled

3 tools perform destructive updates without destructiveHint — run_code deletes at line 98 (scratch.unlink(missing_ok=True)); write_remote_file deletes at line 145 (local.unlink(missing_ok=True)); read_remote_file deletes at line 173 (local.unlink(missing_ok=True))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tool inputs are validated

15/17 tool handlers declare input schemas (88%)

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

Tool handlers catch errors

Only 5/17 tool handlers wrap calls in try/catch (29%)

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

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.

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 8 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/animationsaver-colab-cli-mcp-10k091?variant=verified)](https://m8ven.ai/mcp/animationsaver-colab-cli-mcp-10k091)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: bd431dadbec9d5aa340995d76b7dda26bcbc25fb
code hash: 74465e8ebd9a1f05c2ebc38a0104b17f9591a14ca708827d99e0a6a1b49d4c36
verified: 8/5/2026, 9:00:56 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