WebArcheology-MCP
Related Servers
Alternatives to WebArcheology-MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables reverse engineering of web applications and chat interfaces through browser automation, network traffic capture, and streaming API discovery. Provides comprehensive tools for analyzing network patterns, capturing streaming responses, and automating complex web interactions.1416 npm1ISC
- AlicenseNot gradedqualityBmaintenanceEnables agents to inspect native binaries, JavaScript/Electron apps, .NET assemblies, and websites without source code, trace runtime behavior, and return evidence-backed findings for explaining features or building similar implementations.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables agents to inspect native binaries, JavaScript and Electron apps, .NET assemblies, and websites, returning code, references, and evidence-backed findings for understanding and reimplementing features.377,174 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables agents and terminal users to inspect native binaries, JavaScript/Electron applications, .NET assemblies, and websites, returning code references and evidence-backed findings for understanding and reimplementing features.377,174 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to inspect and reverse engineer native binaries, JavaScript/Electron applications, .NET assemblies, websites, and runtime behavior, returning evidence-backed findings that can be explained, implemented, or tested.4MIT

openamer-reofficial
AlicenseNot gradedqualityCmaintenanceEnables agents and terminals to reverse engineer native binaries, JavaScript/Electron apps, .NET assemblies, and websites, returning findings with supporting evidence and stated limitations. Analysis runs locally, so users can investigate features without source code, explain how they work, and build comparable implementations.MIT
TDQS
Scored across 18 tools
Several tools overlap on the same action: web_audit_api_catalog, web_decompile_bundles, and web_reconstruct_schema all carve API/schema definitions from bundles, and web_extract_vibe_components vs web_synthesize_shadcn both produce React components from a target site. web_clone_offline_mirror and web_optimize_offline_cache also blur together around offline mirroring. The descriptions do add distinguishing detail (OpenAPI vs GraphQL/gRPC vs raw carving), but an agent can easily pick the wrong member of these clusters.
Every tool uses the identical web_<verb>_<object> snake_case pattern (web_audit_api_catalog, web_capture_live_session, web_diff_bundle_releases). The leading verb is always imperative and the remainder names the target artifact. No camelCase or stylistic mixing anywhere in the set.
18 tools is on the heavy side for a single server and pushes into the borderline band; a few (web_inspect_crdt_state, web_decompile_shaders, web_inspect_media_pipeline) are highly specialized niche capabilities. Each is individually justified by the broad 'web archaeology' scope, but consolidation of the overlapping decompile/extract groups would make the surface more manageable.
Coverage of the reverse-engineering domain is remarkably thorough: recon, bundle decompilation, API/schema reconstruction, state, WASM, PWA, media, shaders, fingerprinting, diffing, and e2e harness generation. Minor gaps exist around cross-artifact management — no tool to list/search previously extracted source or a unified report/export — but core lifecycle from recon to reconstruction is covered.