container-mcp (54rt1n/container-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 27 tools. No publisher has claimed this listing.

Emerging

74/100

10 days ago

container-mcp

Item: container-mcp
Rating: 74
Author: M8ven

A podman ubuntu 24.04 container that serves a MCP server; with file, code execution, bash shell, knowledgebase, and more.

→ 54rt1n/container-mcp · listed on pulsemcp

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 push why connect →

Who stands behind it

54rt1n

Source: PulseMCP · also listed on mcp.so, 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

PulseMCPnot scored here mcp.sonot scored here 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

✅

No credential exfiltration, no sensitive file access, no obfuscation

Static analysis found nothing flowing your secrets to unexpected places.

✅

Open source with a license and README

Anyone can audit the code, the license is declared, and the publisher documents what it does.

🔐

You'll be asked for 1 credential: BRAVE_SEARCH_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.

configSANDBOX_ROOT

configMCP_ALLOWED_HOSTS

configMCP_PORT

configMCP_HOST

configCONTAINER

configLOG_LEVEL

configBASE_DIR

configCOMMAND_RESTRICTED

configBASH_ALLOWED_COMMANDSAllowed Commands: Restricted to safe commands configured in

configBASH_TIMEOUT_DEFAULT

configBASH_TIMEOUT_MAX

configPYTHON_MEMORY_LIMIT

configPYTHON_TIMEOUT_DEFAULT

configPYTHON_TIMEOUT_MAX

configFILE_MAX_SIZE_MB

configFILE_ALLOWED_EXTENSIONS

configWEB_ALLOWED_DOMAINS

🔐 secretBRAVE_SEARCH_API_KEY

configWEB_TIMEOUT_DEFAULT

configCMCP_KB_STORAGE_PATH

configKB_TIMEOUT_DEFAULT

configKB_TIMEOUT_MAX

configCMCP_KB_SEARCH_ENABLED

configCMCP_KB_SPARSE_INDEX_PATH

configCMCP_KB_GRAPH_INDEX_PATH

configCMCP_KB_RERANKER_MODEL

configCMCP_KB_SEARCH_RELATION_PREDICATES

configCMCP_KB_SEARCH_GRAPH_NEIGHBOR_LIMIT

configCMCP_LIST_STORAGE_PATH

configMARKET_TIMEOUT_DEFAULT

configMARKET_TIMEOUT_MAX

configRSS_TIMEOUT_DEFAULT

configRSS_TIMEOUT_MAX

configRSS_USER_AGENT

configTOOLS_ENABLE_SYSTEM

configTOOLS_ENABLE_FILE

configTOOLS_ENABLE_WEB

configTOOLS_ENABLE_KB

configTOOLS_ENABLE_LIST

configTOOLS_ENABLE_MARKET

configTOOLS_ENABLE_RSS

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

27/27 tools missing one or more hints — health_check (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); fs_read (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); fs_write (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +24 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

10/27 tools referenced in tests (37%)

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/54rt1n/container-mcp)](https://m8ven.ai/mcp/54rt1n/container-mcp)

Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.

commit: 50acc5e1fae9c3d4ce0328f87f843ba37a3c9759

code hash: 4faa1689a0d39fa45e63d4bed23f1856590163076a8385d8653dbf2e271c22ae

verified: 9/3/2026, 4:35:13 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