WebLoom Engine (webloomhq/engine) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 88 tools. No publisher has claimed this listing.

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

WebLoom Engine

MCP server giving AI agents 86 tools for browser automation via Chrome DevTools Protocol, including navigation, click/fill ladders, network inspection, per-site cracks, and optional marketplace for site-specific knowledge packs.

→ webloomhq/engine· listed on glama

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

webloomhq

Source: Glama

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

Glama

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

// key findings
🚨
Secret credentials may flow to a network call
9 flows detected: ANTHROPIC_API_KEY, GH_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 4 credentials: ANTHROPIC_API_KEY, CAPTCHA_API_KEY, GH_TOKEN, GITHUB_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.
configWEBLOOM_PLAYBOOK
configCHROME_PLAYBOOK
configWEBLOOM_TELEMETRY_URL
configWEBLOOM_ENGINE_TELEMETRY_URL
configWEBLOOM_PROPOSAL_URL
configWEBLOOM_TELEMETRY
configWEBLOOM_AUTO_UPDATEAuto-update (Threads only): ON by default — polls webloom.run/api/threads/<domain>/latest every 6h to pull free Thread patches. Disable via =off. Engine binary itself does NOT auto-update.
configWEBLOOM_AUTO_HEAL
configWEBLOOM_AUTO_SHARE
configWEBLOOM_UPDATE_URL
configVISION_BACKEND
configFLORENCE_MODEL
🔐 secretANTHROPIC_API_KEY
configVISION_CLAUDE_MODEL
configWEBLOOM_THREADS
configWEBLOOM_UPDATE_CHECK_URL
configCAPTCHA_PROVIDER
🔐 secretCAPTCHA_API_KEY
configWEBLOOM_AUTO_RECORD
configWEBLOOM_AUTO_RECORD_PATH
configWEBLOOM_THREAD_DRAFTS_DIR
configWEBLOOM_AUTO_RECORD_MAX
🔐 secretGH_TOKEN
🔐 secretGITHUB_TOKEN
configWEBLOOM_BASE_URL
configWEBLOOM_ENGINE
// 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

88/88 tools missing one or more hints — list_sessions (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_tabs (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); read_tab (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +85 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 10/88 tools referenced in tests (11%)

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/webloomhq/engine)](https://m8ven.ai/mcp/webloomhq/engine)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: dda75cf702a3a7ed044294e68ad94e476f042189
code hash: 4cf7bd502b1c2406b4dd6217b615a01a357b01debb8d8165321206a75dc61e05
verified: 9/1/2026, 6:40:56 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