Evaluation report

• Repository is reachable

  https://github.com/bromoket/x64dbg_mcp @ d8e6cac — ★ 79 · C++ · MIT · last push 4 weeks ago

• Manifest detected

  kind=mcp slug=x64dbg-mcp-server · path=server · source=package.json

• Slug is URL-safe

  "x64dbg-mcp-server" matches /^[a-z0-9][a-z0-9-]{0,62}$/

• Slug is unique within kind

  No collision found for mcp/x64dbg-mcp-server

• Version is semver

  2.3.0

• Description quality

  14 words · 95 chars — OK but more detail helps

• README is present and substantial

  4,851 chars · 6 sections · 4 code blocks

• Tags / topics declared

  14 total — mcp, x64dbg, debugger, reverse-engineering, model-context-protocol, claude (+8)

• README has usage / example sections

  no labeled section but 4 code blocks document usage

• Homepage / docs URL declared

  https://github.com/bromoket/x64dbg_mcp#readme

• Dependencies: known vulnerabilitieswarn

  3 high/critical advisories — @modelcontextprotocol/[email protected] (HIGH: GHSA-345p-7cg4-v4c7) · @modelcontextprotocol/[email protected] (HIGH: GHSA-8r9q-7v3j-jr4g) (+1)

  Update the affected packages, then re-publish. (`npm audit` shows the same data locally.)

• LICENSE file at repo root

  LICENSE

• No sensitive files in the repo

  scanned for .env, credentials.json, *.pem, .ssh/, AWS / GCP configs — none found

• MCP: launch path

  bin: x64dbg-mcp-server · scripts.start

• MCP: @modelcontextprotocol/sdk in dependencies

  pinned at "^1.12.1"

• MCP: SDK version pinned

  pinned at "^1.12.1"

• MCP: ESM package

  "type": "module"

• MCP: server surface

  0 tools

• Tests detectedwarn

  no test/tests/__tests__/spec/t/ dirs, no JVM src/test/, and no JS/TS/Python/Go/Ruby/Elixir test files

  Add tests (even a smoke test). Consumers gauge maintenance quality by their presence.

• CI configuration detectedwarn

  no CI config found (looked for GitHub Actions, CircleCI, GitLab CI, etc.)

  Add a simple workflow (lint + test on PR) — it tells consumers the artifact is built reproducibly.

• Recent activity

  last push 4 weeks ago

This artifact hasn't produced behavioral results yet: the evaluation sandbox couldn't run it (it may need credentials we don't provide, or a build our environment doesn't support). That's a limitation of our environment, not a verdict on the artifact.