Explain how to link this Vibe Monitor installation to the user's account. Call ONLY when the human asks to link this device. Makes no network request.

Checkpoint structural evolution after a meaningful implementation batch. Persists a snapshot and reports stage-aware findings.

Read-only source-based structural duplicate candidates, legacy consumer-reference review, and multi-snapshot code evolution with Git churn; no automatic deletion or causal claims.

Explain one finding with evidence, standards mapping, heuristic disclosure, staged action and over-engineering guard.

Record explicit user feedback about a Vibe Monitor finding. Use only when the user clearly says a warning was useful, wrong, too early, too late, or confusing. Never ask for feedback after every warning.

Read risk trend, evidence-review status and explicitly confirmed Product Intent guidance for one Finding. Includes an unverified baseline for future feedback, never causal attribution.

Return current findings ordered by evolution stage and pressure score. Findings include Do now, Prepare, Do not do yet, and Next trigger.

Create a bounded ARP v1 semantic architecture review request for a finding that explicitly recommends semantic review. The request contains normalized architecture evidence and no raw source code or project path.

Find local legacy compatibility, retired feature markers, disabled branches and possibly unreferenced private functions. Each candidate requires consumer verification; nothing is auto-deleted.

ONLY after a user or agent explicitly states they applied, deferred, or dismissed a specific Vibe recommendation. Record a REPORTED action, not inferred code changes; never claim a fix occurred. Idempotent via stable submissionId.

Read local recommendation→reported action→comparable follow-up→user verification and recurrence history. No project scan or Cloud telemetry. Risk improvement is observational, attribution remains unproven.

Record ONLY explicit user-reported verification for a previously reported action. User affirmation plus regression-test/independent-review evidence type is still not proof of causation. Never fabricate execution or user confirmation.

Read Vibe Monitor's current product-intent context. Inferred values are advisory; explicit values come only from the user's own stated intent.

Read current architecture-evolution status without creating a history snapshot.

Start or resume Vibe Monitor for the current coding session. Can be interrupted or explicitly skipped without preventing coding. For an explicit user Skip request, set mode=skip. Otherwise establishes a bounded project assessment.

Store explicit product-intent facts locally when the user has clearly stated them. Do not turn guesses into explicit intent and do not ask these questions unless an architecture decision materially depends on them.

Skip an in-progress Vibe Monitor Session Start, at the user's explicit request. Cancels active scanning in this MCP server without stopping coding or disabling future monitoring. Agent hosts may expose this tool as an action; Vibe Monitor cannot insert custom buttons in host UI.

Submit one ARP v1 semantic architecture review. Different agents may legitimately return different verdicts. Full model-generated review text stays local; Cloud receives only bounded structured review metadata for comparison and outcome learning.

Get the Vibe Monitor version currently running in this MCP process, the installed current/previous runtime versions, staged update, and update state. A process may still run an older bundle after the installed pointer changes. Use this tool when the user asks which Vibe Monitor version is running or installed. schemaVersion and evidenceVersion are data format versions, NOT the software version.