chatgpt-sol-local-bridge (mingrath/chatgpt-sol-local-bridge) is an MCP server listed on the M8ven Trust Index. It scores 45 out of 100, grade D. It declares 44 tools. No publisher has claimed this listing.

D
Caution
45/100

chatgpt-sol-local-bridge

Enables ChatGPT to securely control a local workstation via an MCP tunnel, exposing 44 tools for file/project editing, git, process supervision, browser automation, and Office document handling across macOS, Linux, and Windows.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we 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

mingrath

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 →

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
⚠️
Tool annotations don’t match behaviour
2 read-only tools perform write/delete/exec — search_text (line 145: spawnSync("rg", args, { encoding: "utf8", maxBuffer: 8 * 1024 * 1024 })); workspace_snapshot (line 100: spawnSync("git", ["rev-parse", "--short", "HEAD"], { cwd: root, encoding: "utf8" }))
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — search_text (line 145: spawnSync("rg", args, { encoding: "utf8", maxBuffer: 8 * 1024 * 1024 }))
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 2 credentials: CONTROL_PLANE_API_KEY, MCP_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.
configAPPROVAL_VERIFIER_COMMAND/absolute/path/to/read-only-approval-verifier
configAPPROVAL_VERIFIER_SHA256pinned sha256 of that executable>
configBODY_LIMIT
configBRIDGE_DENY_PATHS
configBRIDGE_SCRATCH_DIRExpected result: exactly 44 tools, a write/read/edit round trip in a unique directory under , a blocked destructive command, and a successful single-use confirmation.
configBRIDGE_STATE_DIR
configCODEX_BIN
🔐 secretCONTROL_PLANE_API_KEYexport ="sk-..."
configCONTROL_PLANE_TUNNEL_ID
configDEFAULT_WORKSPACE/Users/you/projects
configDISPLAY
configHOST
configINTERCEPTOR_BIN
configLINUX_AUDIO_DEVICE
configMACOS_AUDIO_DEVICE
configMACOS_SCREEN_DEVICE
🔐 secretMCP_TOKEN
configProgramData
configProgramFiles
configProgramFiles(x86)
configSCREEN_SIZE
configTOOL_ENV_ALLOWLIST
configTUNNEL_PROFILE
configWEB_FETCH_ALLOW_HOSTSlocalhost,api.dev.internal.example
configWINDIR
configWINDOWS_AUDIO_DEVICE
configWORKSPACE_ROOTS/Users/you/projects
// quality suggestions

All four hints declared on every tool

44/44 tools missing one or more hints — dom_cdp (missing: idempotentHint); accessibility (missing: idempotentHint); input_event (missing: idempotentHint), +41 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 annotations match behaviour

2 read-only tools perform write/delete/exec — search_text (line 145: spawnSync("rg", args, { encoding: "utf8", maxBuffer: 8 * 1024 * 1024 })); workspace_snapshot (line 100: spawnSync("git", ["rev-parse", "--short", "HEAD"], { cwd: root, encoding: "utf8" }))

Either remove the readOnlyHint:true annotation, or remove the write/delete call from the tool handler.

Destructive tools are labelled

2 tools perform destructive updates without destructiveHint — write_file deletes at line 194 (fs.unlinkSync(tmp)); edit_file deletes at line 194 (fs.unlinkSync(tmp))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — search_text (line 145: spawnSync("rg", args, { encoding: "utf8", maxBuffer: 8 * 1024 * 1024 }))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool inputs are validated

36/44 tool handlers declare input schemas (82%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Shell command execution

14 child_process/subprocess calls in production code — runs shell commands (src/doctor.js:78, src/doctor.js:86, src/doctor.js:116)

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

Tool description accuracy

search_text: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

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/mingrath/chatgpt-sol-local-bridge?variant=verified)](https://m8ven.ai/mcp/mingrath/chatgpt-sol-local-bridge)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 3c7b0c0fffa0e04f4533f871ece3da0064cf6620
code hash: 359c65a6eca9e1c7b49e366c61a1a203150b50f35e9ebfc8f49ef20c6c0ab40e
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