verl-tool (TIGER-AI-Lab/verl-tool) 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
A
Trusted
98/100
12 hours ago

verl-tool

A version of verl to support diverse tool use [TMLR 2026]

→ TIGER-AI-Lab/verl-tool· listed on github_code

Trusted. Deep verification, no outstanding findings, and an established reputation. 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

TIGER-AI-Lab

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
🚨
Secret credentials may flow to a network call
1 flow detected: SERP_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 3 credentials: SERP_API_KEY, BRIGHTDATA_API_KEY, SERPER_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.
🔐 secretSERP_API_KEY
configTOKEN_PATH
configCREDENTIALS_PATH
configSERVICE_ACCOUNT_PATH
configDRIVE_FOLDER_ID
configVERL_LOGGING_LEVEL
configMCP_DEFAULT_SERVER
configMCP_GATEWAY_ADDRESS
configMCP_EVAL_DEBUG_DIR
configVT_TOOL_TYPE
configVT_HOST
configVT_PORT
configVT_WORKERS_PER_TOOL
configVT_MAX_CONCURRENT_REQUESTS
configVT_REQUEST_TIMEOUT
configVT_THREAD_POOL_SIZE
configVT_USE_TQDM
configVT_LOG_LEVEL
configVT_DONE_IF_INVALID
configVT_USE_RAY
configVT_ENABLE_HASHING
configVT_LOG_INTERVAL
🔐 secretBRIGHTDATA_API_KEY
🔐 secretSERPER_API_KEY
configSANDBOX_FUSION_URL
configRETRIEVER_URL
configRETRIEVER_TOPK
configSQL_CACHE_DIR
configNCCL_DEBUG
configTOKENIZERS_PARALLELISM
configCUDA_VISIBLE_DEVICES
configSGLANG_BLOCK_NONZERO_RANK_CHILDREN
configVERL_VLLM_ZMQ_ADDRESSES
configRANK
configWORLD_SIZE
configMASTER_ADDR
configMASTER_PORT
configLOCAL_RANK
configVERL_USE_EXTERNAL_MODULES
configVERL_USE_MODELSCOPE
configVERL_AUTO_PADDING
configVERL_DATAPROTO_SERIALIZATION_METHOD
configVIDEO_MAX_PIXELS
configTORCHCODEC_NUM_THREADS
configFORCE_QWENVL_VIDEO_READER
configVT_WORKER_BASE_URLS
configLLM_AS_A_JUDGE_BASE
configDIST_INIT_METHOD
// 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

54/54 tools missing one or more hints — get_today_date (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_current_datetime (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_current_datetime_utc (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +51 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 test coverage

Only 7/54 tools referenced in tests (13%)

Write tests that reference each tool by name so every tool has at least one test.

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 3 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/tiger-ai-lab-verl-tool-17unxy)](https://m8ven.ai/mcp/tiger-ai-lab-verl-tool-17unxy)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 383d4b1539ba387f94c3a117d3edc06b467c09d1
code hash: c5abb2cb8f3ded219f1bbbf5bcdc453e89521d68f4e6b0ea9205263ff7a7006f
verified: 9/1/2026, 5:43:02 PM
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