letmediff

MCPattested

v0.0.11ISCUpdated 4d agonpm GitHub

MCP server of letmediff.it...allows the agent to show the diff url and receive the diff comments from the server

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build

A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.

34Downloads/wk

1GitHub stars

4d agoLast update

Package

Author

LicenseISC

Version0.0.11

Sourcenpm+mcp-registry

npmletmediff

GitHubpaoloricciuti/letmediff

SBOMCycloneDX 1.6 ↓

Trust Status

85/100Trusted

✓Listed in Forge index+10/10

✓Identity verified · attested build+20/20

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓npm Trusted Publishing (Sigstore)+5/5

—npm maintainer match+0/5

→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusIdentity verified

PublisherUnverified

SignatureUnsigned

Domain—

Provenance✓ Sigstore-verified · 8f80bb3

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface2 tools · none privileged

Security scan✓ Cleanv0.0.11 · todayHow well does this scan work?

EvalsNone

IndexedSep 7, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

2 tools · none privileged

Statically extracted from the published packagev0.0.11 · 2h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

get_urlInvoke this when the users ask you to review the code to get the review URL. You can include multiple steps each should be used to guide the user through the best review possible. After this tool returns you MUST send it to the user and then call the `wait_for_feedback` tool.

Invoke this when the users ask you to review the code to get the review URL. You can include multiple steps each should be used to guide the user through the best review possible. After this tool returns you MUST send it to the user and then call the `wait_for_feedback` tool.

No input schema was published for this tool.

wait_for_feedbackWait for the user to provide feedback on the diff. The tool will return the feedback provided by the user so after it returns assume that's the user telling you what to do and continue as if it was a message in the chat. If the tool times out invoke it again unless the user told you not to do it.

Wait for the user to provide feedback on the diff. The tool will return the feedback provided by the user so after it returns assume that's the user telling you what to do and continue as if it was a message in the chat. If the tool times out invoke it again unless the user told you not to do it.

No input schema was published for this tool.

2 of 2 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server of letmediff.it...allows the agent to show the diff url and receive the diff comments from the server

Keywords

mcp

Alternatives

Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-08 — observed resolution, not a publisher declaration.

60 packages resolved · 10 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

diff9.0.0
tmcp1.20.05 dependencies
- sqids0.3.0
- valibot1.4.2
- json-rpc-2.01.8.0
- uri-template-matcher1.1.2
- @standard-schema/spec1.1.0
memfs4.71.0+3 not drawn11 dependencies
- tslib2.8.1
- thingies2.6.1
- tree-dump1.1.0
- glob-to-regex.js1.2.0
- @jsonjoy.com/util1.9.0+2 not drawn
- @jsonjoy.com/fs-fsa4.71.0+2 not drawn2 dependencies
  - thingies2.6.1shown above
  - @jsonjoy.com/fs-core4.71.0+2 not drawn1 dependency
    thingies2.6.1shown above
- @jsonjoy.com/fs-core4.71.0shown above+2 not drawn
- @jsonjoy.com/fs-node4.71.0+2 not drawn5 dependencies
  - thingies2.6.1shown above
  - glob-to-regex.js1.2.0shown above
  - @jsonjoy.com/fs-core4.71.0shown above+2 not drawn
  - @jsonjoy.com/fs-print4.71.0+1 not drawn1 dependency
    tree-dump1.1.0shown above
  - @jsonjoy.com/fs-snapshot4.71.0+4 not drawn
- @jsonjoy.com/fs-print4.71.0shown above+1 not drawn
- @jsonjoy.com/json-pack1.21.0+5 not drawn3 dependencies
  - thingies2.6.1shown above
  - tree-dump1.1.0shown above
  - @jsonjoy.com/util1.9.0shown above+2 not drawn
- @jsonjoy.com/fs-snapshot4.71.0shown above+4 not drawn
valibot1.4.2shown above
typescript6.0.3
eventsource4.1.1+1 not drawn
isomorphic-git1.41.9+11 not drawn
@tmcp/adapter-valibot0.1.6+1 not drawn2 dependencies
- @standard-schema/spec1.1.0shown above
- valibot1.4.2shown above
@tmcp/transport-stdio0.5.0+1 not drawn
@jsonjoy.com/fs-snapshot4.71.0shown above+4 not drawn

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

18 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 18

string_decoder ^1.3.0 — required by readable-stream@4.7.0package cap reached
@jsonjoy.com/codegen 17.67.0 — required by @jsonjoy.com/util@17.67.0package cap reached
hyperdyperid ^1.2.0 — required by @jsonjoy.com/json-pack@17.67.0package cap reached
@jsonjoy.com/util 17.67.0 — required by @jsonjoy.com/json-pack@17.67.0package cap reached
@jsonjoy.com/base64 17.67.0 — required by @jsonjoy.com/json-pack@17.67.0package cap reached
@jsonjoy.com/buffers 17.67.0 — required by @jsonjoy.com/json-pack@17.67.0package cap reached
@jsonjoy.com/codegen 17.67.0 — required by @jsonjoy.com/json-pack@17.67.0package cap reached
@jsonjoy.com/json-pointer 17.67.0 — required by @jsonjoy.com/json-pack@17.67.0package cap reached
@jsonjoy.com/util ^1.9.0 — required by @jsonjoy.com/json-pointer@1.0.2package cap reached
@jsonjoy.com/codegen ^1.0.0 — required by @jsonjoy.com/json-pointer@1.0.2package cap reached
isarray ^2.0.5 — required by to-buffer@1.2.2package cap reached
safe-buffer ^5.2.1 — required by to-buffer@1.2.2package cap reached

+6 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

letmediff

Tools

Tools exposed

Dependency tree

Declared but not resolved