ViewDoctor MCP server
io.github.KamnevVladimir/viewdoctor·v0.1.7·2 starsLocal SwiftUI changed/staged checks with compact agent output and multi-module ownership.
2 stars
Reviews
Write oneNobody has reviewed ViewDoctor yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
ViewDoctor tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 53 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How ViewDoctor compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 80/100
- higher than 60% of 4,461 AI and agents servers
- GitHub stars
- 2
- more than 65% of 2,713 AI and agents servers
Install ViewDoctor in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the ViewDoctor repository's README, as published. We do not edit it. Read it on GitHub
ViewDoctor
Check SwiftUI diffs with module ownership attached.
ViewDoctor maps modules from Swift Package Manager, Tuist, Xcode projects, and common source layouts before it scans SwiftUI code. Run it after a human or coding agent changes a diff; the result stays local and can be read as terminal text, compact agent JSON, full versioned JSON, or SARIF.
Modules/Profile/Sources/ProfileView.swift:42:18: warning: VD001 [tuist:Modules/Profile/Profile]: DateFormatter is constructed inside a body property.
ViewDoctor: 1 finding(s) in 12 file(s), 4 module(s).The review loop
A small generated diff should not require sending the repository back to a general model just to look for three known SwiftUI risks. ViewDoctor gives those checks stable rule IDs, exact locations, module ownership, and bounded output:
edit -> scan changed files -> fix findings -> verify once
verbose human context; full JSON keeps explanations for integrations.
- It reads source locally and has no telemetry.
- Manifest-derived identifiers keep findings useful in large repositories.
- Agent JSON keeps the location, module, message, and fix without repeating
- Deterministic ordering and exit codes make the same command useful in CI.
ViewDoctor complements the Swift compiler, SwiftLint, Periphery, and Instruments. It does not replace builds, profiling, or architecture review.
Install and run
Requires Swift 6.2 or newer for source builds.
git clone https://github.com/KamnevVladimir/ViewDoctor.git
cd ViewDoctor
swift build -c release
.build/release/viewdoctor scan /path/to/projectAnalyze only the current git diff—the recommended mode for coding agents:
viewdoctor scan . --git-diff --format agent
viewdoctor scan . --base origin/main --format agent--git-diff includes tracked changes and new untracked Swift files. A newly generated view is therefore not skipped just because it has not been added to Git yet.
Run a strict pre-commit checkpoint against the index only:
viewdoctor scan . --staged --fail-on warningInspect discovered modules and dependencies:
viewdoctor graph .Generate GitHub Code Scanning output:
viewdoctor scan . --base origin/main --format sarif > viewdoctor.sarifDiscover commands and the installed version without opening the README:
viewdoctor --help
viewdoctor --versionChanged files, pre-commit, and CI
These are separate checkpoints rather than aliases:
Use --fail-on warning when warnings must block a hook or CI job. The default remains error, so adopting ViewDoctor does not silently turn every warning into a breaking gate.
Multi-module architecture
ViewDoctor builds a normalized graph from all manifests it discovers:
When providers overlap, the longest matching source root wins. The graph model exposes a reverse dependency-cone operation for integrations and future affected-module rules. The current three source rules still scan only the selected files; they do not pretend to validate unchanged dependents.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-10-30downgradeA → Bscore 80
ViewDoctor: common questions
- Is ViewDoctor MCP server safe?
- Mostly: it is graded B (80/100). Read the ViewDoctor safety report
- Does ViewDoctor need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is ViewDoctor maintained?
- The last commit was 60 days ago (2026-09-06). The latest release is v0.1.7.
- What can I use instead of ViewDoctor?
- Servers from other publishers that do the same job: Doc Bridge MCP server, PaperBanana MCP server and llmtrim MCP server.
- How does ViewDoctor compare with other AI and agents MCP servers?
- safety score 80/100 (higher than 60% of 4,461 AI and agents servers); github stars 2 (more than 65% of 2,713 AI and agents servers). Full comparison.
Alternatives to ViewDoctor
Same job from other publishers: the closest match first, then the best rated.
- Doc BridgeResolve documentation ownership, edit roots, checks, and human handoffs before an agent edits code.not reviewedEstablishedA
- PaperBananaGenerate academic diagrams and statistical plots from text using multi-agent AI.not reviewedEstablishedA
- llmtrimMCP server and proxy that compresses LLM prompts, tool output, and replies to cut token cost.not reviewedEstablishedA
- three.ws BrainList LLM providers and run chat completions through the three.ws multi-provider router.not reviewedEstablishedB
- KilnSpawn an object into existence: describe it, and your agent designs it, checks it, and 3D prints it.not reviewedEstablishedB