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

veritas

VERITAS: A Multi-Agent Co-Scientist for Verifiable Image-Derived Hypothesis Testing

→ LucZot/veritas· 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

LucZot

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 2 credentials: OPENROUTER_API_KEY, OPENAI_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.
configCODE_EXEC_OUTPUT_DIR
configCODE_EXEC_TIMEOUT
configCODE_EXEC_MAX_MEMORY_MB
configDATASET_PATH
configACDC_DATA_ROOT
configACDC_ROOT
configPHASE2B_RESULTS_DB
configSAT_REPO_PATH
configSAT_CHECKPOINT_DIR
configVERITAS_MCP_CONNECT_TIMEOUT
configCODE_EXEC_WORKSPACE_DIR
configBIO_DATA_ROOTexport =/path/to/your/data # add to ~/.bashrc to make it permanent
configVERITAS_OUTPUT_DIR
configLLM_PROVIDER
configOLLAMA_KEEP_ALIVE
configOLLAMA_BASE_URL
configOLLAMA_MODEL
configOLLAMA_ENABLE_THINKING
configOPENROUTER_BASE_URL
🔐 secretOPENROUTER_API_KEYexport =sk-or-...
🔐 secretOPENAI_API_KEY
configOPENROUTER_HTTP_REFERER
configOPENROUTER_X_TITLE
configOPENROUTER_MODEL
configVERITAS_MAX_OUTPUT_TOKENS
configVERITAS_LLM_TIMEOUT
configOPENAI_BASE_URL
configOLLAMA_CONTEXT_LENGTH
configCODE_EXEC_CLEANUP_FAILED
configSHOW_THINKING_IN_OUTPUT
configWORKFLOW_OUTPUT_PATH
configWORKFLOW_PROMPT_VERBOSITY
configWORKFLOW_ENABLE_CRITIC
configWORKFLOW_ENABLE_CRITIC_PHASE1
configWORKFLOW_ENABLE_CRITIC_PHASE3
configDATASET_METADATA
configVERITAS_PHASE_TIMEOUT
configVERITAS_CONTEXT_LENGTH
configWORKFLOW_CONFIG_FILE
configPI_MODEL
configIMAGING_DISCUSSION_MODEL
configSTATISTICIAN_DISCUSSION_MODEL
configWORKFLOW_TEMPERATURE
configHYPOTHESIS
configCRITIC_MODEL
configIMAGING_EXECUTION_MODEL
configSTATISTICIAN_CODING_MODEL
// 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

14/14 tools missing one or more hints — dynamic_tool_140 (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); call_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); execute_code_file (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +11 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.

Shell command execution

3 child_process/subprocess calls in production code — runs shell commands (mcp_servers/code_execution/execution_engine.py:216, mcp_servers/code_execution/execution_engine.py:228, mcp_servers/code_execution/execution_engine.py:871)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

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/luczot-veritas-1pmgp5)](https://m8ven.ai/mcp/luczot-veritas-1pmgp5)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 17dbdc96cef23c29a4efbf0291de6d6295908a17
code hash: 92c6ec33c8591b7b2fd85adfb97350cdc8da1e533995cee6ca3cdf15cccde4a2
verified: 8/12/2026, 7:51:11 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