openclaw_with_jupyterlab_and_rstudio (icejean/openclaw_with_jupyterlab_and_rstudio) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Emerging
74/100
12 days ago

openclaw_with_jupyterlab_and_rstudio

OpenClaw + JupyterLab + RStudio 一体化数据分析环境

→ icejean/openclaw_with_jupyterlab_and_rstudio· listed on github_code

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

icejean

Source: github_code

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

GitHub

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

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: R_API_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.
configJUPYTER_MCP_TIMEOUT120 kernel 代码执行超时（秒）
configR2PY_SHARED_DIR覆盖: 环境变量
configJUPYTER_SHARED_DIR（Python 侧单独覆盖）
confighttp_proxyjupyter-mcp NotebookClient 通过 REST API 写 .ipynb 时走代理 —— 已自动临时屏蔽 /https_proxy
confighttps_proxyjupyter-mcp NotebookClient 通过 REST API 写 .ipynb 时走代理 —— 已自动临时屏蔽 http_proxy/
configJUPYTER_MCP_HOST127.0.0.1 MCP Server 监听地址（HTTP 模式用，stdio 模式无需监听）
configJUPYTER_MCP_PORT0 MCP Server 端口，0 = stdio 模式（推荐）
configR_API_HOST127.0.0.1 R API 地址
configR_API_PORT8161 R API 端口
🔐 secretR_API_TOKEN空 R API 认证 Token（空=不启用）
configR_SHARED_DIR同 R2PY_SHARED_DIR R 侧单独覆盖
configMCP_PORT0 MCP Server 端口，0 = stdio 模式（推荐）
configJPY_CONNECTION_FILE
configJPY_SESSION_NAME
// 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

20/20 tools missing one or more hints — handle_call_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); run_code (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_objects (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +17 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.

Tests exist

No test files found

Add tests that exercise each declared tool.

No eval / new Function

2 eval() or new Function() calls — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

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/icejean-openclaw-with-jupyterlab-and-rstudio-oppytp)](https://m8ven.ai/mcp/icejean-openclaw-with-jupyterlab-and-rstudio-oppytp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 3c618be5f39e953db5296528e204a6709db4a0ad
code hash: 527df8def7cac016bdfc97c48031fa502e0de7ef721dfaa3bf9e928421dcd09d
verified: 8/19/2026, 9:21:03 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