Mobius MCP Server

mobius-mcp npm v1.1.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP server exposing live browser runtime events to AI coding agents

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/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
Moderate
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 = 95/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 − 5 = 95. 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
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 46

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

  • get_logs_sincereads sensitive data
  • get_network_requestsingests untrusted input
  • cancel_jobno sensitive capability
  • capture_accessibility_treeno sensitive capability
  • capture_domno sensitive capability
  • capture_elementno sensitive capability
  • capture_full_pageno sensitive capability
  • clear_logsno sensitive capability
  • clickno sensitive capability
  • enable_captureno sensitive capability
Show 36 more tools ↓
  • end_debug_sessionno sensitive capability
  • evaluate_jsno sensitive capability
  • export_harno sensitive capability
  • findno sensitive capability
  • get_capture_settingsno sensitive capability
  • get_connected_tabsno sensitive capability
  • get_job_resultno sensitive capability
  • get_job_statusno sensitive capability
  • get_recent_errorsno sensitive capability
  • get_recent_logsno sensitive capability
  • get_request_bodyno sensitive capability
  • get_response_bodyno sensitive capability
  • hoverno sensitive capability
  • list_tabsno sensitive capability
  • mobius_diagnoseno sensitive capability
  • navigate_tono sensitive capability
  • open_tabno sensitive capability
  • press_keyno sensitive capability
  • reload_tabno sensitive capability
  • run_sequenceno sensitive capability
  • scroll_byno sensitive capability
  • scroll_tono sensitive capability
  • select_optionno sensitive capability
  • set_active_tabno sensitive capability
  • set_checkboxno sensitive capability
  • snapshot_pageno sensitive capability
  • start_cpu_profileno sensitive capability
  • start_debug_sessionno sensitive capability
  • start_memory_profileno sensitive capability
  • switch_tabno sensitive capability
  • take_screenshotno sensitive capability
  • type_textno sensitive capability
  • wait_for_console_errorno sensitive capability
  • wait_for_elementno sensitive capability
  • wait_for_navigationno sensitive capability
  • wait_for_requestno sensitive capability

What this scan could not see

Versions 3

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
v1.1.0 latest A 95/100 0 1.13.0 2026-09-09
v1.0.2 A 95/100 0 1.12.1 2026-08-02
v1.0.1 A 95/100 0 1.12.1 2026-07-29

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 · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mobius-mcp/badge.svg)](https://mcptrustchecker.com/registry/mobius-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/mobius-mcp"><img src="https://mcptrustchecker.com/registry/mobius-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mobius-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 mobius-mcp --online

Use the free API → How scoring works

More in Developer Tools