angeo/module-mcp-server

Healthy and reasonable to adopt, with strong package hygiene and active early release cadence. The main caveats are minimal repository adoption and a CI workflow without declared token permissions; the project is only 49 days old, so long-term maintenance is not yet established.

Latest 2.2.2

Packagist

84%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. With no backlog this is not an abandonment signal, but it also provides little evidence of an established user or maintainer feedback loop.

Repo popularity

The repository has only 1 star, 1 fork, and 0 watchers, so independent adoption evidence is minimal. This is a caution rather than a severe concern because the package itself is only 49 days old and popularity is supporting evidence.

Repo tooling

Composer build tooling is present, but no security scanning tool was detected. That is a modest transparency gap, partly offset by the repository's tests, CI workflow, and security policy.

Token permissions

The only CI workflow lacks top-level token permissions, so its GitHub token scope is not explicitly minimized. No workflow requests top-level write access, limiting the practical concern.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

No maintainer information available.

Direct Dependencies

Dependency	Last Release	Score
magento/framework Version >=103.0.6 <104	—	—
magento/module-store Version >=101.1.6 <102	—	—
magento/module-catalog Version >=104.0.6 <105	—	—
magento/module-customer Version >=103.0.6 <104	—	—
magento/module-integration Version >=100.4.6 <101	—	—