# wet-mcp - Doramagic AI Context Pack > Purpose: pre-work context for the user's host AI. This pack does not prove that the project has been installed, run, or validated. ## Project - canonical_name: `n24q02m/wet-mcp` - capability: Open-source MCP server for AI agents: web search, content extraction, and library docs -- 5-strategy scraping, runs without API keys. - expected_user_outcome: Open-source MCP server for AI agents: web search, content extraction, and library docs -- 5-strategy scraping, runs without API keys. ## Operating Boundaries - Do not claim that the project has been installed, run, called through an API, or used on local files unless separate evidence proves it. - Project facts must come from repo evidence, Claim Graph, or explicit source references. - When a capability is not verified, mark it as unverified instead of completing it as fact. - publish_status: `publishable` - blocking_gaps: none --- ## Doramagic Context Augmentation The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints. ## Human Manual Outline Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph. Host AI hard rules: - Do not treat page titles, section order, summaries, or importance values as factual project evidence. - When explaining the Human Manual outline, state that it is only a reading route or salience signal. - Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph. - **Overview & System Architecture**: importance `high` - source_paths: README.md, docs/ARCHITECTURE.md, src/wet_mcp/server.py, src/wet_mcp/__main__.py, src/wet_mcp/relay_setup.py - **Core Tools & Feature Surface**: importance `high` - source_paths: src/wet_mcp/server.py, src/wet_mcp/sources/docs.py, src/wet_mcp/sources/crawler.py, src/wet_mcp/sources/searxng.py, src/wet_mcp/sources/search_backends.py - **Configuration, Model Chains & Deployment**: importance `high` - source_paths: src/wet_mcp/config.py, src/wet_mcp/llm.py, src/wet_mcp/embedder.py, src/wet_mcp/reranker.py, src/wet_mcp/searxng_runner.py - **Data Layer, Sync & Security**: importance `high` - source_paths: src/wet_mcp/db.py, src/wet_mcp/db_cf.py, src/wet_mcp/backends/d1.py, src/wet_mcp/backends/vectorize.py, src/wet_mcp/cache.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `a68e8573a831f64e288d3b0146908882c31e959b` - inspected_files: `Dockerfile`, `README.md`, `docker-compose.yml`, `package.json`, `pyproject.toml`, `uv.lock`, `docs/ARCHITECTURE.md`, `docs/BENCHMARKS.md`, `docs/benchmarks/v1_phase2_baseline.json`, `docs/cf-template.md`, `docs/docs-search.md`, `docs/interact.md`, `docs/migration.md`, `docs/passport.md`, `src/wet_mcp/__init__.py`, `src/wet_mcp/__main__.py`, `src/wet_mcp/alembic/env.py`, `src/wet_mcp/alembic/versions/docs_001_baseline.py`, `src/wet_mcp/alembic/versions/docs_002_libraries.py`, `src/wet_mcp/alembic/versions/docs_003_project_context.py` Host AI hard rules: - Without repo_clone_verified=true, do not claim that the source code has been read. - Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts. - Without quick_start_verified=true, do not claim that the Quick Start path has run successfully. ## Doramagic Pitfall Constraints These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes. ### Constraint 1: Configuration risk requires verification - Trigger: Project evidence flags a configuration risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: packet_text.keyword_scan | https://github.com/n24q02m/wet-mcp - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: Installation risk requires verification - Trigger: Developers should check this installation risk before relying on the project: Dependency Dashboard - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Dependency Dashboard. Context: Observed when using python, docker - Why it matters: Developers may fail before the first successful local run: Dependency Dashboard - Evidence: failure_mode_cluster:github_issue | https://github.com/n24q02m/wet-mcp/issues/231 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Installation risk requires verification - Trigger: Developers should check this installation risk before relying on the project: v3.3.0-beta.18 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v3.3.0-beta.18. Context: Observed when using python, docker - Why it matters: Upgrade or migration may change expected behavior: v3.3.0-beta.18 - Evidence: failure_mode_cluster:github_release | https://github.com/n24q02m/wet-mcp/releases/tag/v3.3.0-beta.18 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Configuration risk requires verification - Trigger: Project evidence flags a configuration risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: capability.host_targets | https://github.com/n24q02m/wet-mcp - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Configuration risk requires verification - Trigger: Developers should check this configuration risk before relying on the project: v3.3.0-beta.12 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v3.3.0-beta.12. Context: Observed when using docker - Why it matters: Upgrade or migration may change expected behavior: v3.3.0-beta.12 - Evidence: failure_mode_cluster:github_release | https://github.com/n24q02m/wet-mcp/releases/tag/v3.3.0-beta.12 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: Configuration risk requires verification - Trigger: Developers should check this configuration risk before relying on the project: v3.3.0-beta.13 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v3.3.0-beta.13. Context: Source discussion did not expose a precise runtime context. - Why it matters: Upgrade or migration may change expected behavior: v3.3.0-beta.13 - Evidence: failure_mode_cluster:github_release | https://github.com/n24q02m/wet-mcp/releases/tag/v3.3.0-beta.13 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: Configuration risk requires verification - Trigger: Developers should check this configuration risk before relying on the project: v3.3.0-beta.15 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v3.3.0-beta.15. Context: Source discussion did not expose a precise runtime context. - Why it matters: Upgrade or migration may change expected behavior: v3.3.0-beta.15 - Evidence: failure_mode_cluster:github_release | https://github.com/n24q02m/wet-mcp/releases/tag/v3.3.0-beta.15 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 8: Configuration risk requires verification - Trigger: Developers should check this configuration risk before relying on the project: v3.3.0-beta.16 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v3.3.0-beta.16. Context: Source discussion did not expose a precise runtime context. - Why it matters: Upgrade or migration may change expected behavior: v3.3.0-beta.16 - Evidence: failure_mode_cluster:github_release | https://github.com/n24q02m/wet-mcp/releases/tag/v3.3.0-beta.16 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 9: Configuration risk requires verification - Trigger: Developers should check this configuration risk before relying on the project: v3.3.0-beta.20 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v3.3.0-beta.20. Context: Source discussion did not expose a precise runtime context. - Why it matters: Upgrade or migration may change expected behavior: v3.3.0-beta.20 - Evidence: failure_mode_cluster:github_release | https://github.com/n24q02m/wet-mcp/releases/tag/v3.3.0-beta.20 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 10: Capability evidence risk requires verification - Trigger: README/documentation is current enough for a first validation pass. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: capability.assumptions | https://github.com/n24q02m/wet-mcp - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.