Warning

30/100

9 days ago

RunBeacon

Item: RunBeacon
Rating: 30
Author: M8ven

RunBeacon is an MCP server that turns long-running local and SSH commands into tracked jobs. It provides event-driven monitoring, a live dashboard, and a resident daemon for reliable execution and cancellation.

→ Liyuchen0118/RunBeacon · listed on glama

Warning. Serious findings were identified. Review the full report before connecting. 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

Liyuchen0118

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

🚨

Hardcoded credentials detected

1 live-looking API key in source: 1 AWS access key

⚠️

Known vulnerabilities in dependencies: 1 high

Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.

🔐

You'll be asked for 4 credentials: AUDIT_ENCRYPTION_KEY, RUNBEACON_GITHUB_TOKEN, SSH_TEST_KEY, SSH_TEST_PASS

These are read from process.env at runtime. Make sure you trust where they’ll be sent.

// known CVEs in dependencies1 high1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highjs-yaml@4.3.0GHSA-5p4m-2wfm-xmqj

JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026-59870 fix not backported

lowuuid@11.1.0GHSA-w5hq-g745-h8pq

uuid: Missing buffer bounds check in v3/v5/v6 when buf is provided

Depend on this server? Get alerted when its CVEs change.Watch this server free →

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

🔐 secretAUDIT_ENCRYPTION_KEY

configAWS_DEFAULT_REGION

configAWS_REGION

configCLAUDE_PLUGIN_DATA

configDBUS_SESSION_BUS_ADDRESS

configDISPLAY

configENABLE_PROACTIVE_MONITORING

configJAVA_HOME

configLOG_LEVELcodex mcp add console-automation --env =warn -- node "$PWD/dist/mcp/server.js"

configMCP_AUTO_CLEANUP

configMCP_CLEANUP_INTERVAL

configMCP_DEBUG_LOGleave and MCP_LOG_DIR unset unless diagnostics are explicitly required;

configMCP_LOG_DIRleave MCP_DEBUG_LOG and unset unless diagnostics are explicitly required;

configMCP_MAX_SESSIONS

configMCP_SERVER_MODE

configMCP_SERVER_PATH

configMCP_SESSION_PERSISTENCE

configMCP_SESSION_PERSISTENCE_PATH

configMCP_SESSION_TIMEOUT

configPGPASSWORD

configPGSSLMODE

configPLUGIN_DATA

configProgramFiles

configProgramFiles(x86)

configRJM_BUILD_VERSION

configRJM_CANCEL_GRACE_MS

configRJM_INLINE_MANAGER

configRJM_MAX_CONCURRENT_JOBS

configRJM_MAX_OUTPUT_BYTES

configRJM_MAX_RETAINED_JOBS

configRJM_PERSIST_DEBOUNCE_MS

configRJM_PERSIST_METADATA

configRJM_PERSIST_OUTPUT

configRJM_SSH_HANDSHAKE_ATTEMPTS

configRJM_SSH_READY_TIMEOUT_MS

configRJM_SSH_RETRY_BASE_DELAY_MS

configRJM_STATE_PATH

configRUNBEACON_GITHUB_CREDENTIAL_SOURCE

🔐 secretRUNBEACON_GITHUB_TOKEN

configRUNBEACON_GITHUB_USERNAME

configRUNBEACON_SERVER_PATH

configSHELL

configSSH_AUTH_SOCK

configSSH_TEST_HOST

🔐 secretSSH_TEST_KEY

🔐 secretSSH_TEST_PASS

configSSH_TEST_PORT

configSSH_TEST_USER

configSystemRoot

configTERM

configTF_PLUGIN_CACHE_DIR

// quality suggestions

Tool annotations

16/56 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

40/56 tools missing one or more hints — console_create_session (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); console_send_input (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); console_send_key (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +37 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.

No hardcoded API keys

1 live-looking API key in source: 1 AWS access key

Move secrets to environment variables (process.env.X) or your secret manager.

Tool test coverage

Only 4/56 tools referenced in tests (7%)

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

No eval / new Function

6 eval() or new Function() calls — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Shell command execution

140 child_process/subprocess calls in production code — runs shell commands (src/protocols/BMCProtocol.ts:215, src/protocols/BMCProtocol.ts:409, src/core/ConsoleManager.ts:6594)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

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 7 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 Verified](https://m8ven.ai/badge/mcp/liyuchen0118-runbeacon-142tp3?variant=verified)](https://m8ven.ai/mcp/liyuchen0118-runbeacon-142tp3)

Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.

commit: 61a81d40e00e256565e515c91e26df27936d7f9c

code hash: 6fc2049c1f93ba44420280ec89c4b0f56a29e4e6470957d70b60f5a54270881e

verified: 8/10/2026, 4:10:21 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