ARBuilder (Quantum3-Labs/ARBuilder) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 55 tools. No publisher has claimed this listing.

C
Emerging
74/100

ARBuilder

AI-powered code generator for the Arbitrum ecosystem with 19 MCP tools. Generates Stylus smart contracts (Rust/WASM), SDK bridging code, full-stack dApps, and Orbit chain deployments using RAG-based retrieval over Arbitrum documentation.

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

⚡ 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

Quantum3-Labs

Source: Glama · also listed on github_topic

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

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
13 flows detected: AUTH_SECRET, ARBBUILDER_ADMIN_SECRET, GITHUB_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 5 credentials: INFURA_KEY, OPENROUTER_API_KEY, GITHUB_TOKEN, DEPLOY_PRIVATE_KEY, NVIDIA_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.
🔐 secretINFURA_KEY
configSHOULD_FORK
🔐 secretOPENROUTER_API_KEY
configDEFAULT_MODEL
configFALLBACK_MODEL
configRAW_DATA_DIR
configPROCESSED_DATA_DIR
🔐 secretGITHUB_TOKEN
configREVIEW_MODEL
configSEPOLIA_RPC
🔐 secretDEPLOY_PRIVATE_KEY
configDEFAULT_EMBEDDING
🔐 secretNVIDIA_API_KEY
configDEFAULT_CROSS_ENCODER
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployNEXT_PUBLIC_TURNSTILE_SITE_KEY
// 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

55/55 tools missing one or more hints — get_stylus_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); generate_stylus_code (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ask_stylus (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +52 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

18/55 tools referenced in tests (33%)

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/quantum3-labs/arbuilder)](https://m8ven.ai/mcp/quantum3-labs/arbuilder)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: bb34efbdb9babc1b7e831f3d00ebba6ed045a42b
code hash: 7196d635d8e38734102bb34a17cc81911c94d21286e3f53afc2d441a913a53e5
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