nexus (bingStat/nexus) is an MCP server listed on the M8ven Trust Index. It scores 37 out of 100, grade F. It declares 17 tools. No publisher has claimed this listing.

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 pushwhy connect →

Who stands behind it

bingStat

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 →

Install from

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
🚨
Reads files from sensitive locations
Touches: /etc/nexus-chatgpt-remote.env
🔐
You'll be asked for 5 credentials: NEXUS_MCP_BEARER_TOKEN, NEXUS_WEB_COUNCIL_TOKEN, NEXUS_V3_ADMIN_KEY, NEXUS_CHATGPT_API_KEY, NEXUS_V5_SSH_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes17 tools · 11 behind config

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

write_workspace

Create or completely overwrite one file inside an opened DevSpace workspace.

edit_workspace

Edit one workspace file by applying exact text replacements.

list_workspace

List a directory inside an opened DevSpace workspace without invoking a shell.

grep_workspace

Search workspace file contents with the upstream DevSpace grep tool.

glob_workspace

Find workspace files by glob pattern without invoking a shell.

terminate_workspace_process

Terminate one running DevSpace process session in the named workspace.

self_testbehind config

Check Nexus v5 route configuration and device reachability. Use this to distinguish control-plane/device failures from a client authentication problem.

list_devicesbehind config

List all Nexus fleet devices and their live capabilities (devspace/shell).

get_devicebehind config

Get details and public key for a specific named device.

fleet_statusbehind config

Get real-time operational status for configured Nexus v5 logical devices.

execute_commandbehind config

Execute a shell command on an explicitly named Nexus device (e.g. victus, thinkcenter, oracle, vsc).

execute_batchbehind config

Execute up to 16 shell commands concurrently across different named devices.

open_workspacebehind config

Open an upstream DevSpace project folder or managed worktree on a named device.

read_workspacebehind config

Read a file through the DevSpace runtime on the target device.

apply_workspace_patchbehind config

Apply a code patch in an opened DevSpace workspace on the target device.

exec_workspace_commandbehind config

Run a command inside an opened DevSpace workspace.

write_workspace_stdinbehind config

Interact with or send stdin to a running DevSpace process session.

// 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.
configNEXUS_DEVSPACE_ALLOWED_ROOTS
configNEXUS_DEVSPACE_STATE_DIR
configNEXUS_V3_MCP_BIND
configNEXUS_V3_MCP_PORT
🔐 secretNEXUS_MCP_BEARER_TOKEN
configNEXUS_BROWSER_PROFILE_ROOT
configNEXUS_AGENT_BROWSER_COMMAND
configNEXUS_COUNCIL_WORKTREE_ROOT
🔐 secretNEXUS_WEB_COUNCIL_TOKEN
configNEXUS_V3_CONFIG
configNEXUS_WINDOWS_SHELL
🔐 secretNEXUS_V3_ADMIN_KEY
configNEXUS_V3_REGISTRY_URL
configNEXUS_V3_REGION
configNEXUS_V3_BIND
configNEXUS_V3_BROKER_PORT
configNEXUS_V3_BROKER_DB
🔐 secretNEXUS_CHATGPT_API_KEY
configNEXUS_CHATGPT_PUBLIC_BASE_URL
configNEXUS_CHATGPT_BIND
configNEXUS_CHATGPT_PORT
configNEXUS_DEVSPACE_BRIDGE
configNEXUS_NODE
configNEXUS_V3_REGISTRY_PORT
configNEXUS_V3_REGISTRY_DB
configNEXUS_V3_ALLOW_DANGEROUS
configNEXUS_V5_API_BIND
configNEXUS_V5_API_PORT
configNEXUS_V5_ROUTES
configNEXUS_V5_TOKEN_FILE
🔐 secretNEXUS_V5_SSH_KEY
configNEXUS_V5_KNOWN_HOSTS
configNEXUS_V5_CONFIG
configNEXUS_V3_ENV_FILE
configGITHUB_SHA
configGITHUB_RUN_ID
configNEXUS_V3_CN_BROKER_URL
configNEXUS_V3_EU_BROKER_URL
configNEXUS_OPS_CONFIG
configNEXUS_TELEGRAM_PROXY
// quality suggestions

Tool annotations

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

11/28 tools missing one or more hints — self_test (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_devices (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_device (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +8 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

17/28 tools referenced in tests (61%)

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

No access to sensitive paths

Reads sensitive paths: /etc/nexus-chatgpt-remote.env

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

Secrets not logged

1 secret value sent to print

Redact or omit secret values from log output.

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 6 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/bingstat/nexus?variant=verified)](https://m8ven.ai/mcp/bingstat/nexus)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: db3c15c746d7ca84aebdaabf79df10280ed9a2f0
code hash: 527eb046d8cc7852adac7a402f2e15203fb48961be59cb88810c71caea43e53f
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