mcp-devbridge (ShiningSugar35/mcp-devbridge) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

C
Emerging
74/100
6 days ago

mcp-devbridge

Exposes a local development project as a secure MCP server over a stable HTTPS URL via Cloudflare tunnel, with configurable access permissions and 33 development tools for file, command, Git, and process operations.

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

Who stands behind it

ShiningSugar35

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

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// 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 5 credentials: CODEBASE_BRIDGE_HTTP_TOKEN, CODEXPRO_ALLOW_NO_HTTP_TOKEN, CODEXPRO_HTTP_TOKEN, CODEXPRO_REQUIRE_HTTP_TOKEN, CODEXPRO_WINDOWS_BRIDGE_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.
configCODEBASE_BRIDGE_ALLOWED_ROOTS
🔐 secretCODEBASE_BRIDGE_HTTP_TOKEN
configCODEBASE_BRIDGE_REPO_ROOT
configCODEXPRO_ALLOWED_ROOTS
configCODEXPRO_ALLOW_HOME
🔐 secretCODEXPRO_ALLOW_NO_HTTP_TOKEN
configCODEXPRO_ANALYSISSet =0 to disable repository analysis without changing the rest of the connector.
configCODEXPRO_ANALYSIS_MAX_ANALYZED_FILES
configCODEXPRO_ANALYSIS_MAX_INVENTORY_FILES
configCODEXPRO_ANALYSIS_MAX_RELATIONSHIPS
configCODEXPRO_ANALYSIS_MAX_SCANNED_BYTES
configCODEXPRO_ANALYSIS_MAX_SYMBOLS
configCODEXPRO_BASH_MODE
configCODEXPRO_BASH_SESSION_ID
configCODEXPRO_BASH_TRANSCRIPT
configCODEXPRO_BLOCKED_GLOBS
configCODEXPRO_CODEX_DIR
configCODEXPRO_CODEX_SESSIONS
configCODEXPRO_CONNECTION_TEST
configCODEXPRO_CONTEXT_DIR
configCODEXPRO_HOME
configCODEXPRO_HOST
configCODEXPRO_HOSTNAME
configCODEXPRO_HTTP_SESSION_TTL_MS
🔐 secretCODEXPRO_HTTP_TOKEN
configCODEXPRO_INHERIT_ENV
configCODEXPRO_LOG_REQUESTS
configCODEXPRO_LOG_TOOL_CALLS
configCODEXPRO_MAX_HTTP_SESSIONS
configCODEXPRO_MAX_OUTPUT_BYTES
configCODEXPRO_MAX_READ_BYTES
configCODEXPRO_MAX_SEARCH_RESULTS
configCODEXPRO_MAX_WRITE_BYTES
configCODEXPRO_MODE
configCODEXPRO_PORT
configCODEXPRO_PUBLIC_HOSTNAME
configCODEXPRO_REQUIRE_BASH_SESSION
🔐 secretCODEXPRO_REQUIRE_HTTP_TOKEN
configCODEXPRO_ROOT
configCODEXPRO_SHELL
configCODEXPRO_TOOL_CARDS1 codexpro start
configCODEXPRO_TOOL_MODE
configCODEXPRO_TUNNEL
configCODEXPRO_TUNNEL_MODE
configCODEXPRO_WIDGET_DOMAIN
🔐 secretCODEXPRO_WINDOWS_BRIDGE_TOKEN
configCODEXPRO_WINDOWS_BRIDGE_URL
configCODEXPRO_WINDOWS_CALL_TIMEOUT_MS
configCODEXPRO_WINDOWS_DESKTOP_ALLOW
configCODEXPRO_WINDOWS_PROFILE
configCODEXPRO_WRITE_MODEGeneric writes are hidden unless =workspace.
configHOST
configNGROK_DOMAIN
configSHELL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

3/3 tools missing one or more hints — windows_backend_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); windows_list_tools (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); windows_call (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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.

Tests exist

No test files found

Add tests that exercise each declared tool.

No eval / new Function

1 eval() or new Function() call — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Shell command execution

9 child_process/subprocess calls in production code — runs shell commands (src/server.ts:676, src/server.ts:687, src/bashOps.ts:318)

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 5 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/shiningsugar35-mcp-devbridge-1o8x8f)](https://m8ven.ai/mcp/shiningsugar35-mcp-devbridge-1o8x8f)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 2b6ff10d264fbf83d05a41ac85d7f0b8db036387
code hash: 6ea3e2277ff91b1ae1dbaa9d1509998a01b44bf274f0d8413d11f52f6b5b4f3a
verified: 8/20/2026, 3:06:58 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