dittu
NPM · @MANISHTAMANG/DITTU
Clone any website's frontend into Next.js or Astro and verify it with pixel diffs.
Available components
Last scanned (4 hours ago)
Scores higher than 52% of npm servers
Category Browser Automation
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 48 of 180 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 396 tokens (~132/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
- Security disclosure: unverified → pass ▲ functional
- 2 Nov 26 0
- Security disclosure: pass → unverified ▼ functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
- Stability: 0.13 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.3.0 functional
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 25 Oct 26 +1
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.1.0 → 0.2.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@manishtamang/dittu@0.3.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 180 packages
| Packages resolved | 180 |
|---|---|
| Stale | 48 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
clone_website Clone website frontend ~251
Clone a website's frontend (markup, original CSS, fonts, images, scroll animations) into a static preview plus Next.js and Astro projects, then score it against the original with pixel diffs at desktop and mobile widths. Takes ~1 minute per page (several minutes with build=true). Returns output paths and scores (percent identical).
| Name | Type | Req | Description |
|---|---|---|---|
| build | boolean | – | Also npm install + build + score the generated apps (slow, default false) |
| frameworks | array | – | Projects to generate (default next + astro) |
| outDir | string | – | Output directory (default ./dittu-out/<host>) |
| pages | integer | – | Crawl up to n same-site pages (default 1) |
| remove | array | – | CSS selectors to drop (cookie banners, chat widgets) |
| styling | string | – | css keeps the original stylesheet (default); tailwind converts class rules to Tailwind utilities wherever that renders identically and keeps the rest as CSS |
| url | string | yes | Page to clone, e.g. https://gole.codes |
| verify | boolean | – | Score the clone against the original (default true) |
| waitMs | integer | – | Extra wait after load in ms |
No output schema declared.
No examples provided.
read_report Read clone report ~45
Manifest and latest scores of a clone: pages, targets, per-width scores, diff image paths, worst regions.
| Name | Type | Req | Description |
|---|---|---|---|
| outDir | string | yes | Output directory of a previous clone |
No output schema declared.
No examples provided.
verify_clone Verify a clone ~100
Re-score an existing clone against the original site (e.g. after refactoring the generated components). Use targets ["next"] or ["astro"] to build and score a generated project. A score drop means the refactor changed rendering.
| Name | Type | Req | Description |
|---|---|---|---|
| outDir | string | yes | Output directory of a previous clone |
| targets | array | – | What to score (default preview) |
| widths | array | – | Viewport widths (default 1440, 390) |
No output schema declared.
No examples provided.
How do I install the dittu MCP server?
dittu runs locally as an npm package, launched with npx -y @manishtamang/dittu. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @manishtamang/dittu
claude mcp add manish-tamang-dittu -- npx -y @manishtamang/dittu
What is the dittu MCP server?
dittu is an MCP server listed in the public MCP registry as io.github.Manish-Tamang/dittu. Clone any website's frontend into Next.js or Astro and verify it with pixel diffs. This page covers its npm package (@manishtamang/dittu).
Is the dittu MCP server safe to use?
dittu scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the dittu MCP server expose?
dittu exposes 3 tools: clone_website, verify_clone, read_report. Their descriptions and schemas cost roughly 396 tokens of context every time the server is loaded.
Is the dittu MCP server still maintained?
dittu is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the dittu MCP server under?
dittu declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.