chatgpt-mac-bridge (mingrath/chatgpt-mac-bridge) is an MCP server listed on the M8ven Trust Index. It scores 66 out of 100, grade C. It declares 39 tools. No publisher has claimed this listing.

C
Caution
66/100

chatgpt-mac-bridge

Gives ChatGPT Web hands on your Mac — files, git, terminal, browser, and windows via MCP, with outbound-only tunnel and delete protection.

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
1 read-only tool performs write/delete/exec — search_text (line 42: spawnSync("rg", args, { encoding: "utf8", maxBuffer: 4 * 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 1 credential: 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.
configCODEX_BIN
configCOMMAND_TIMEOUT_MS
configDEFAULT_WORKSPACEOr set WORKSPACE_ROOTS / in .env (see .env.example). Writes are limited to $HOME and /tmp. ~/.ssh, Keychains, /System, and /usr are refused.
configHOSTThe MCP port binds 127.0.0.1. Do not change to 0.0.0.0 unless you know why.
🔐 secretMCP_TOKENOptional in .env requires Authorization: Bearer … on /mcp.
configWORKSPACE_ROOTSOr set / DEFAULT_WORKSPACE in .env (see .env.example). Writes are limited to $HOME and /tmp. ~/.ssh, Keychains, /System, and /usr are refused.
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

All four hints declared on every tool

39/39 tools missing one or more hints — dom_cdp (missing: idempotentHint); accessibility (missing: idempotentHint); input_event (missing: idempotentHint), +36 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

1 read-only tool performs write/delete/exec — search_text (line 42: spawnSync("rg", args, { encoding: "utf8", maxBuffer: 4 * 1024 * 1024 }))

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

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — screen_record deletes at line 137 (fs.unlinkSync(flag))

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.

Tool inputs are validated

31/39 tool handlers declare input schemas (79%)

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

Tests exist

No test files found

Add tests that exercise each declared tool.

Shell command execution

6 child_process/subprocess calls in production code — runs shell commands (src/doctor.js:27, src/doctor.js:32, src/doctor.js:38)

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

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