Skip to main content
Glama
README.md
# WebArcheology MCP (`webarcheology-mcp`)

> 🏛️ **Official Organization Transfer Notice**  
> This project has been officially transferred to the **[KRC Labs](https://github.com/KRC-Labs)** engineering organization.  
> All active runtime engineering, public releases, and technical documentation are maintained under KRC Labs.

---

### 🔗 Official Resources & Portal (공식 링크 및 리소스)

- 🏛️ **Organization (공식 조직)**: [https://github.com/KRC-Labs](https://github.com/KRC-Labs)
- 🌐 **Interactive Systems Showcase (실시간 시스템 쇼케이스)**: [https://krc-labs.github.io/](https://krc-labs.github.io/)
- 📊 **Status & Release Hub (시스템 현황 & 변경 로그)**: [https://github.com/KRC-Labs/status](https://github.com/KRC-Labs/status)

---

<details open>
<summary><b>🌐 Multi-Language Official Notice (10 Languages / 10개국어 지원 안내)</b></summary>
<br>

| Flag / Language | Official Migration Notice (1:1 Translation) |
| :---: | :--- |
| 🇺🇸 **English** | This project has been officially transferred to **[KRC Labs](https://github.com/KRC-Labs)**. All active runtimes and documentation are maintained under KRC Labs. |
| 🇰🇷 **한국어** | 이 프로젝트는 공식 엔지니어링 조직인 **[KRC Labs](https://github.com/KRC-Labs)**로 정식 이관되었습니다. 모든 시스템 런타임 및 기술 문서는 KRC Labs에서 통합 관리됩니다. |
| 🇯🇵 **日本語** | 本プロジェクトは公式エンジニアリング組織 **[KRC Labs](https://github.com/KRC-Labs)** へ正式移管されました。すべてのランタイム開発および技術文書は KRC Labs にて管理されます。 |
| 🇨🇳 **简体中文** | 本项目已正式迁移至官方工程组织 **[KRC Labs](https://github.com/KRC-Labs)**。所有活跃的运行时工程与技术文档均由 KRC Labs 统一维护。 |
| 🇩🇪 **Deutsch** | Dieses Projekt wurde offiziell an **[KRC Labs](https://github.com/KRC-Labs)** übertragen. Sämtliche Laufzeitentwicklungen und Dokumentationen werden von KRC Labs verwaltet. |
| 🇫🇷 **Français** | Ce projet a été officiellement transféré à l'organisation d'ingénierie **[KRC Labs](https://github.com/KRC-Labs)**. L'ensemble des runtimes et de la documentation est géré par KRC Labs. |
| 🇪🇸 **Español** | Este proyecto ha sido transferido oficialmente a **[KRC Labs](https://github.com/KRC-Labs)**. Toda la ingeniería de ejecución activa y la documentación técnica se gestionan en KRC Labs. |
| 🇷🇺 **Русский** | Данный проект официально передан инженерной организации **[KRC Labs](https://github.com/KRC-Labs)**. Вся разработка и техническая документация поддерживаются в KRC Labs. |
| 🇮🇳 **हिन्दी** | यह प्रोजेक्ट आधिकारिक रूप से **[KRC Labs](https://github.com/KRC-Labs)** को स्थानांतरित कर दिया गया है। सभी रनटाइम और तकनीकी दस्तावेज़ KRC Labs द्वारा प्रबंधित किए जाते हैं। |
| 🇵🇹 **Português** | Este projeto foi oficialmente transferido para a **[KRC Labs](https://github.com/KRC-Labs)**. Todo o desenvolvimento ativo e a documentação técnica são mantidos pela KRC Labs. |

</details>

---

<sub>© KRC Labs. All rights reserved.</sub>

TDQS

B3.2/5.0

Scored across 18 tools

Disambiguation3/5

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.

Naming Consistency5/5

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.

Tool Count3/5

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.

Completeness4/5

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.