acme-commerce-copilot (lasso-collab/acme-commerce-copilot) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 23 tools. No publisher has claimed this listing.

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

acme-commerce-copilot

Multi-agent customer support copilot for e-commerce. A LangGraph supervisor routes each conversation to specialist agents for orders, refunds, research, analytics and policy, with RAG over the internal knowledge base and MCP-backed warehouse access.

→ lasso-collab/acme-commerce-copilot· listed on github_repo_search

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

lasso-collab

Source: github_repo_search

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

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
2 flows detected: PAYMENTS_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 6 credentials: PAYMENTS_API_KEY, OPENAI_API_KEY, ANTHROPIC_API_KEY, GOOGLE_API_KEY, TAVILY_API_KEY, ADMIN_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.
configSUPERVISOR_MODEL
configREFUNDS_MODEL
configKNOWLEDGE_MODEL
configPROMPT_REGISTRY_URL
configINVOICE_FEED
configMCP_REGISTRY_PATH
configNOTIFY_WEBHOOK_URL
configMAIL_API
configPAYMENTS_API_BASE
🔐 secretPAYMENTS_API_KEY
🔐 secretOPENAI_API_KEY
🔐 secretANTHROPIC_API_KEY
🔐 secretGOOGLE_API_KEY
🔐 secretTAVILY_API_KEY
🔐 secretADMIN_API_KEY
configCHROMA_PATH
configFAISS_INDEX_PATH
configKB_PATH
configLLM_MODEL
configORDERS_MODEL
configGRAPH_RECURSION_LIMIT
configINVOICE_MODEL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPOSTGRES_DSN
deployWAREHOUSE_DSN
deployREDIS_URL
// 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

23/23 tools missing one or more hints — run_python (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); run_shell (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); read_document (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +20 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 2/23 tools referenced in tests (9%)

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

Secrets stay with their owner

2 secrets sent to a request target we could not resolve (PAYMENTS_API_KEY → dynamic, PAYMENTS_API_KEY → dynamic) — often a configured endpoint, not necessarily third-party

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

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/lasso-collab/acme-commerce-copilot)](https://m8ven.ai/mcp/lasso-collab/acme-commerce-copilot)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: b911e703d5023e7f5b6b2ec4548e1eb0846ec1de
code hash: a0fbb52965715b7ce99e2d1c0ed37b7f7f75f6df527877075c4cc1d065651e50
verified: 9/11/2026, 11:20:13 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