liferay-docker-manager (peterrichards-lr/liferay-docker-manager) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 8 tools. No publisher has claimed this listing.

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

liferay-docker-manager

A professional command-line orchestrator for quickly standing up Liferay Portal and DXP environments using Docker Compose.

→ peterrichards-lr/liferay-docker-manager· 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

peterrichards-lr

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

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
3 flows detected: GITHUB_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 2 credentials: GITHUB_TOKEN, LFT_CLIENT_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.
configLDM_MCP_CIRCUIT_BREAKER_MAX_ACTIONS
configLDM_MCP_CIRCUIT_BREAKER_WINDOW
configLDM_ALLOW_ROOT
configGITHUB_ACTIONS
configLDM_DRY_RUN
configLDM_REPO_OWNER
configLDM_REPO_NAME
configPYTEST_CURRENT_TEST
configGITHUB_PAT
🔐 secretGITHUB_TOKEN
configLDM_HOME
configSUDO_USER
configLDM_TEST_MODE
configLDM_WORKSPACE
configLDM_NO_KEYRING
configSHELL
configLDM_COMMON_DIR
configLDM_IGNORE_DOCKER
configLOGNAME
configLFT_SERVER_URL
configNGROK_AUTHTOKEN
configLDM_SAMPLES_PATH
configLDM_DEV_MODE
configLDM_SSL_PORT
configLDM_HTTP_PORT
configLDM_ADMIN_PORT
configLDM_LFR_TUNNEL_BIN
configLDM_LFR_TUNNEL_INSTALL_CMD
configLFR_TUNNEL_INSTALL_CMD
🔐 secretLFT_CLIENT_TOKEN
configLFT_EVENT
configLFT_NODE_ID
configLFT_SECONDS_REMAINING
configLFT_FAILOVER_REGION
configLFT_SUBDOMAIN
configLDM_FRAGMENT_PATCH_TIMEOUT
configLDM_FAIL_ON_STALE_PATCHES
configLDM_CPU_IDLE_THRESHOLD
configLDM_CPU_IDLE_CHECKS
configLDM_FORWARD_PREFIXES
// 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

8/8 tools missing one or more hints — get_projects (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_logs (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); start_project (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +5 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.

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 2 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/peterrichards-lr/liferay-docker-manager)](https://m8ven.ai/mcp/peterrichards-lr/liferay-docker-manager)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: d79c341ec9e53e24abe25f457fbe2795d3ed367c
code hash: aee7031c3d57f45b5546c9a3a0dbf5e8a411fde680c96807368b488dff940eda
verified: 9/2/2026, 7:11:14 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