Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Sahib-Sawhney-WH/looking-glass-mcp

NPM · LOOKING-GLASS-MCP · SCANNED SEP 20

AI-native browser for agents. 71 tools with self-healing, semantic extraction, vault CLI.

Available components

0 this week 70 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security80
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects uuid 9.0.1, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 33 of 100 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency71
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Cryptographically verified build provenance (signed, bound to Sahib-Sawhney-WH/LookingGlass). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 173 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability47
  • AI-judged instruction clarity (poor).Fail
  • Tool/resource definitions use about 1870 tokens (~26/item across 71 items; 71 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage33
  • 0% of tools have a non-trivial description (not blank, and not just the tool's name).Fail
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "vault_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 71 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.Sahib-Sawhney-WH/looking-glass-mcp server?

io.github.Sahib-Sawhney-WH/looking-glass-mcp runs locally as an npm package, launched with npx -y looking-glass-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · looking-glass-mcp

# add to Claude Code
claude mcp add sahib-sawhney-wh-looking-glass-mcp -- npx -y looking-glass-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "sahib-sawhney-wh-looking-glass-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "looking-glass-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "sahib-sawhney-wh-looking-glass-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "looking-glass-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add sahib-sawhney-wh-looking-glass-mcp -- npx -y looking-glass-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sahib-sawhney-wh-looking-glass-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "looking-glass-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add sahib-sawhney-wh-looking-glass-mcp --command npx --arg -y --arg looking-glass-mcp
# ~/.hermes/config.yaml
mcp_servers:
  sahib-sawhney-wh-looking-glass-mcp:
    command: "npx"
    args: ["-y", "looking-glass-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "sahib-sawhney-wh-looking-glass-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "looking-glass-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add sahib-sawhney-wh-looking-glass-mcp -t stdio -c npx -a -y looking-glass-mcp
// mcp.json
{
  "mcpServers": {
    "sahib-sawhney-wh-looking-glass-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "looking-glass-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/looking-glass-mcp@3.1.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Sahib-Sawhney-WH/LookingGlass
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Sahib-Sawhney-WH/LookingGlass/.github/workflows/publish.yml@refs/tags/v3.1.1
Rekor log index 1199806681
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:9b3b39e3f7cbd5960c9675d1f0a63a5d210c83f8039476a78152472a29aa0775e68586c0a954b4b0ffab47ae22221dec9e40e5914ae4a963f4e4ddf53

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 100 packages
Packages resolved 100
Deprecated 1
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 71 exposed · ~1,870 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
session_export_playwright ~43

No description provided.

NameTypeReqDescription
outputPathstringCustom output path for the .spec.ts file
sessionIdstringyesSession ID to export (use session_list to find IDs)

No output schema declared.

No examples provided.

session_list ~5

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

session_replay ~24

No description provided.

NameTypeReqDescription
sessionIdstringyesSession ID (first 8 chars or full UUID)

No output schema declared.

No examples provided.

session_start ~15

No description provided.

NameTypeReqDescription
namestringOptional session name

No output schema declared.

No examples provided.

test_accessibility_audit ~8

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

test_assert ~47

No description provided.

NameTypeReqDescription
attributestringAttribute name (for hasAttribute)
expectedstring|numberExpected value
selectorstringCSS selector
typestringyesAssertion type

No output schema declared.

No examples provided.

test_auth_flow ~108

No description provided.

NameTypeReqDescription
passwordSelectorstringyesCSS selector for password input
passwordValuestringyesPassword
submitSelectorstringyesCSS selector for submit/login button
urlstringyesLogin page URL
usernameSelectorstringyesCSS selector for username/email input
usernameValuestringyesUsername or email
waitForSelectorstringWait for this element after login
waitForUrlstringWait for URL to match after login

No output schema declared.

No examples provided.

test_chaos ~59

No description provided.

NameTypeReqDescription
delayMsnumberMax delay for random-delays profile (default: 2000ms)
profilestringyesChaos condition to apply
urlPatternstringURL pattern for block-api profile (default: /api/)

No output schema declared.

No examples provided.

test_chaos_clear ~8

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

test_fill_form ~19

No description provided.

NameTypeReqDescription
fieldsarrayyesArray of form fields to fill

No output schema declared.

No examples provided.

test_generate_assertions ~7

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

test_scenario_run ~89

No description provided.

NameTypeReqDescription
baseUrlstringBase URL (e.g., http://localhost:3000)
dataSetsarrayData sets for parameterized testing. The scenario runs once per data set with {{variable}} substitution.
namestringyesScenario name
stepsarrayyesArray of test steps to execute. Steps can use {{variable}} placeholders when dataSets is provided.

No output schema declared.

No examples provided.

test_scenario_status ~7

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

test_stop_watch ~6

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

test_watch_events ~49

No description provided.

NameTypeReqDescription
eventsarrayyesEvent types to watch
maxEventsnumberMaximum events to capture (default: 1000)
urlPatternstringFilter network events by URL pattern

No output schema declared.

No examples provided.

vault_delete ~16

No description provided.

NameTypeReqDescription
profilestringyesProfile name to delete

No output schema declared.

No examples provided.

vault_inject ~24

No description provided.

NameTypeReqDescription
profilestringyesVault profile whose fields to inject into the current page form

No output schema declared.

No examples provided.

vault_list ~5

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

vault_login ~33

No description provided.

NameTypeReqDescription
profilestringyesVault profile to use for login
urlstringURL to navigate to before login (optional)

No output schema declared.

No examples provided.

visual_baseline ~26

No description provided.

NameTypeReqDescription
namestringyesBaseline name (e.g., "homepage", "login-form")

No output schema declared.

No examples provided.

visual_compare ~18

No description provided.

NameTypeReqDescription
namestringyesBaseline name to compare against

No output schema declared.

No examples provided.

Common questions

What is the io.github.Sahib-Sawhney-WH/looking-glass-mcp server?

io.github.Sahib-Sawhney-WH/looking-glass-mcp is listed in the public MCP registry as io.github.Sahib-Sawhney-WH/looking-glass-mcp. AI-native browser for agents. 71 tools with self-healing, semantic extraction, vault CLI. This page covers its npm package (looking-glass-mcp).

Is the io.github.Sahib-Sawhney-WH/looking-glass-mcp server safe to use?

io.github.Sahib-Sawhney-WH/looking-glass-mcp scores 70 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.Sahib-Sawhney-WH/looking-glass-mcp server expose?

io.github.Sahib-Sawhney-WH/looking-glass-mcp exposes 71 tools: browser_navigate, browser_go_back, browser_go_forward, browser_click, browser_type, and 66 more. Their descriptions and schemas cost roughly 1,870 tokens of context every time the server is loaded.

Is the io.github.Sahib-Sawhney-WH/looking-glass-mcp server still maintained?

io.github.Sahib-Sawhney-WH/looking-glass-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.Sahib-Sawhney-WH/looking-glass-mcp server under?

io.github.Sahib-Sawhney-WH/looking-glass-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.