Letmediff MCP
NPM · LETMEDIFF · SCANNED SEP 26
The official Letmediff MCP server helping you review your code with an agent first workflow
Available components
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
- 33 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to paoloricciuti/letmediff). View diagnostics → Pass
- Clear OSI-approved license (ISC).Pass
- Actively maintained (last published 22 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright), so the captured schema is incomplete.Unverified
Stability & Change Management0
- Stability not yet verified: one of the two schema captures we compare could not list the server's tools (the server declared tools, or its tool listing failed outright). Comparing them would report every tool as removed, or find nothing to compare at all.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).Unverified
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 4 categories
Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Letmediff MCP server?
Letmediff MCP runs locally as an npm package, launched with npx -y letmediff. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · letmediff
claude mcp add it-letmediff-mcp -- npx -y letmediff
{
"mcpServers": {
"it-letmediff-mcp": {
"command": "npx",
"args": [
"-y",
"letmediff"
]
}
}
} {
"servers": {
"it-letmediff-mcp": {
"command": "npx",
"args": [
"-y",
"letmediff"
]
}
}
} codex mcp add it-letmediff-mcp -- npx -y letmediff
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"it-letmediff-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"letmediff"
],
"enabled": true
}
}
} openclaw mcp add it-letmediff-mcp --command npx --arg -y --arg letmediff
mcp_servers:
it-letmediff-mcp:
command: "npx"
args: ["-y", "letmediff"] {
"McpServers": {
"it-letmediff-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"letmediff"
]
}
}
} assistant mcp add it-letmediff-mcp -t stdio -c npx -a -y letmediff
{
"mcpServers": {
"it-letmediff-mcp": {
"command": "npx",
"args": [
"-y",
"letmediff"
]
}
}
} 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.
- 25 Sept 26 −13
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 23 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 26 Sept 2026 · Analysed npm/letmediff@0.0.11
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | paoloricciuti/letmediff |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/paoloricciuti/letmediff/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 2698180403 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:bd98482d41fb7c23871733ff0d34173df5ab031503adf394aff7b1bb1b85a8b7b22b3dfc5824a80f1b113914823b2abfadd601410c46462dff75c2cf6 |
Background: How many MCP packages publish verified provenance →
Dependencies 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 33 |
| 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 →
The sandbox run completed and this package exposed no tools.
What is the Letmediff MCP server?
Letmediff MCP is listed in the public MCP registry as it.letmediff/mcp. The official Letmediff MCP server helping you review your code with an agent first workflow. This page covers its npm package (letmediff).
Is the Letmediff MCP server safe to use?
Letmediff MCP scores 53 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Letmediff MCP server expose?
Letmediff MCP exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.
Is the Letmediff MCP server still maintained?
Letmediff MCP is still listed as active in the MCP registry. We last reached this channel on 26 September 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 Letmediff MCP server under?
Letmediff MCP declares the ISC licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.