Mmcp.market

Snag List Defect Handover Signoff MCP server

by theluckystrike·io.github.theluckystrike/snag-list-defect-handover-signoff·v0.21.0
No reviews yet

Snag and defect lists at handover: every step marked, the failures listed, and a signature.

B73/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B73/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Snag List Defect Handover Signoff yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Snag List Defect Handover Signoff tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it

no findings
  • –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 qualitystatic API keys via environment variables6/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 73/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install directly

The registry entry has no remote endpoint or installable package.

Snag List Defect Handover Signoff: common questions

Is Snag List Defect Handover Signoff MCP server safe?
Mostly: it is graded B (73/100). Read the Snag List Defect Handover Signoff safety report
Does Snag List Defect Handover Signoff need an API key?
Yes. The registry entry asks for MCP_LICENSE_KEY.
Is Snag List Defect Handover Signoff maintained?
The last commit was in the last day (2026-09-19). The latest release is v0.21.0.

More from theluckystrike →