Foxbridge MCP Server

foxbridge-mcp npm v0.1.2

Published by sinamohsenifar — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

FoxBridge — an MCP server + Firefox extension that lets an AI assistant read and drive your real, logged-in Firefox: tabs, DOM, cookies (incl. httpOnly), sessions, storage, and page APIs. Plus on-disk profile reading (cookies, history, sessions, localStor

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 7

high Tool "eval_js" exposes command/code executionMTC-CAP-001

Tool "eval_js" appears to run shell commands or evaluate code (keyword "eval" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool eval_js

high Tool "ff_eval" exposes command/code executionMTC-CAP-001

Tool "ff_eval" appears to run shell commands or evaluate code (keyword "eval" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool ff_eval

high Dynamic code execution in server code (dist/driver.js)MTC-SRC-001

In the server's implementation (`dist/driver.js:275`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const fn = new Function(`return (async () => { ${src.includes("return") ? src : "return (" + src + ")"} })(

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/driver.js

high Shell/command execution in server code (extension/background.js)MTC-SRC-002

In the server's implementation (`extension/background.js:54`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: origin). async function exec(tabId, code) { try { const res = await browser.tabs.executeScript(tabId, { code });

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server extension/background.js

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([ff_fetch, ff_download]) co-exist with external-action tools ([eval_js, ff_eval]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [ff_fetch, ff_download] → sinks [eval_js, ff_eval]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow ff_fetch → eval_js

low Mutating tool "eval_js" declares no destructiveHintMTC-CAP-005

Tool "eval_js" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool eval_js

low Mutating tool "ff_eval" declares no destructiveHintMTC-CAP-005

Tool "ff_eval" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool ff_eval

Tools 52

Each tool and what it can reach — statically extracted from the published source.

  • eval_jsruns code / shell
  • ff_downloadingests untrusted input
  • ff_evalruns code / shell
  • ff_fetchingests untrusted input
  • browser_startno sensitive capability
  • clear_cookiesno sensitive capability
  • clear_disk_cacheno sensitive capability
  • clear_web_storageno sensitive capability
  • clickno sensitive capability
  • close_browserno sensitive capability
Show 42 more tools ↓
  • close_tabno sensitive capability
  • ff_activate_tabno sensitive capability
  • ff_clear_networkno sensitive capability
  • ff_clickno sensitive capability
  • ff_close_tabno sensitive capability
  • ff_get_cookiesno sensitive capability
  • ff_list_downloadsno sensitive capability
  • ff_list_tabsno sensitive capability
  • ff_navigateno sensitive capability
  • ff_networkno sensitive capability
  • ff_open_tabno sensitive capability
  • ff_read_pageno sensitive capability
  • ff_reloadno sensitive capability
  • ff_screenshotno sensitive capability
  • ff_scrollno sensitive capability
  • ff_statusno sensitive capability
  • ff_typeno sensitive capability
  • ff_wait_forno sensitive capability
  • get_bookmarksno sensitive capability
  • get_cache_infono sensitive capability
  • get_cookiesno sensitive capability
  • get_historyno sensitive capability
  • get_live_cookiesno sensitive capability
  • get_local_storageno sensitive capability
  • get_sessionsno sensitive capability
  • go_backno sensitive capability
  • go_forwardno sensitive capability
  • hoverno sensitive capability
  • list_profilesno sensitive capability
  • list_tabsno sensitive capability
  • navigateno sensitive capability
  • open_tabno sensitive capability
  • press_keyno sensitive capability
  • read_pageno sensitive capability
  • reloadno sensitive capability
  • screenshotno sensitive capability
  • scrollno sensitive capability
  • select_optionno sensitive capability
  • set_cookieno sensitive capability
  • switch_tabno sensitive capability
  • type_textno sensitive capability
  • wait_forno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.2 latest A 93/100 7 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/foxbridge-mcp/badge.svg)](https://mcptrustchecker.com/registry/foxbridge-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/foxbridge-mcp"><img src="https://mcptrustchecker.com/registry/foxbridge-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/foxbridge-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan foxbridge-mcp --online

Use the free API → How scoring works

More in Browser Automation