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

AIRepositories

→ arunsadhasivam/AIRepositories· 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

arunsadhasivam

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
✅
23 tools verified — handlers match their declared behaviour
3 read-only tools verified — handlers contain no write/delete/exec
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 5 credentials: STREAM_API_KEY, STREAM_API_SECRET, ANTHROPIC_API_KEY, NEO4J_PASSWORD, 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.
configPHOENIX_WORKING_DIR
configPHOENIX_TMP_DIR
configCHROMA_PATH
configCOLLECTION_NAME
configTEXT_EMBEDDING_MODEL
configLLM_MODEL
🔐 secretSTREAM_API_KEY
🔐 secretSTREAM_API_SECRET
🔐 secretANTHROPIC_API_KEY
configAURA_INSTANCENAME
configNEO4J_URI
configNEO4J_USERNAME
🔐 secretNEO4J_PASSWORD
configNEO4J_DATABASE
🔐 secretOPENAI_API_KEY
configOPENAI_ENDPOINT
configWEAVIATE_URL
configWEAVIATE_CLASS
configDB_HOST
configDB_PORT
configDB_NAME
configMAX_FILE_SIZE
configGUADRAIL_WARNING_MESSAGE
configGUADRAIL_TOPIC_CONTENT
configDB_SUPERUSER
configDB_SUPERUSER_PWD
configSOLR_PORT
configSOLR_CORE
configOLLAMA_BASE_URL
configREDIS_HOST
configREDIS_PORT
configSOLR_HOST
configMULTIQUERY_MAX_QUERY_GEN_LIMIT
configTOP_K
configDLQ_LOG_PATH
configDOC_CHUNK_SIZE
configDOC_CHUNK_OVERLAP
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployREDIS_URL
// quality suggestions

Tool annotations

3/23 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

20/23 tools missing one or more hints — tool_process_text (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); tool_get_count (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); tool_print_count_html (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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 0/23 tools referenced in tests (0%)

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

Shell command execution

3 child_process/subprocess calls in production code — runs shell commands (Projects/MCP/CODE/LOCAL_RAG_REST_API/mcp/mcp_server.py:95, Projects/MCP/CODE/LOCAL_RAG_REST_API/agents/MathClassificationAgent.py:68, Projects/PG_VECTOR/LOCAL_RAG_REST_API/agents/MathClassificationAgent.py:49)

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

Secrets not logged

9 secret values sent to console.log

Redact or omit secret values from log output.

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 6 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/arunsadhasivam-airepositories-39n9p9)](https://m8ven.ai/mcp/arunsadhasivam-airepositories-39n9p9)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: cd98f23a79954febb263cb9590c83e90a01d203a
code hash: 859b8bbbd76dc2da09ada7ed7d7aa63ed9691be70525f6663c8713a68168bdab
verified: 8/18/2026, 9:20:23 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