shadow-monitor-mcp
Related Servers
Alternatives to shadow-monitor-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI coding assistants to visually inspect local web pages by providing screenshots, console errors, and sanitized DOM snapshots.14 npmMIT
- AlicenseNot gradedqualityAmaintenanceGives AI coding agents eyes into running applications by recording browser activity and providing session investigation tools for debugging.6 npm3MIT
- FlicenseBqualityBmaintenanceEnables AI agents to record and time-travel through DOM mutations, inspect and interact with live pages, capture screenshots, and diagnose UI disappearance or layout changes through a 34-tool MCP interface.34-
- AlicenseBqualityAmaintenanceEnables AI agents to debug code and automate browsers using Chrome DevTools Protocol, supporting breakpoints, variable inspection, and replayable interaction recording.35389 npm16MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to locally parse and analyze HAR files through read-only MCP tools, including searching requests, discovering endpoints, tracing values, detecting auth and API patterns, comparing requests, and exporting redacted cURL commands.-
- AlicenseBqualityCmaintenanceEnables AI agents to inspect and control a live Chromium browser for frontend debugging, providing console logs, network requests, DOM snapshots, and accessibility analysis.198 npmMIT
TDQS
Scored across 11 tools
Most tools target a clear, distinct retrieval path: loading/checking, network search/detail, console detail, and user-action replay. The main ambiguity is among bundle_metadata, bundle_overview, and get_semantics, which all surface summary-level bundle information, though their descriptions clarify different use cases.
The naming is largely consistent, with lowercase snake_case and a dominant verb_noun pattern like load_bundle, check_bundle, find_errors, search_network, and get_*. bundle_metadata and bundle_overview deviate slightly by leading with the noun, but the overall pattern is still predictable and readable.
11 tools is well-scoped for a diagnostic bundle inspection server. Each tool corresponds to a meaningful stage or data type in the workflow, from validation and loading to overview, error discovery, network/console drill-down, user actions, replay, and semantics.
The tool set covers the core diagnostic workflow comprehensively: load/validate bundles, orient with overview/semantics, search network and errors, fetch event details, and replay user actions. Minor gaps exist, such as no general non-error console search and no explicit bundle unload/cleanup, but they do not break the primary use case.