zzop MCP server
Deterministic cross-repo contract analysis for AI agents: frontend calls vs backend endpoints.
A88/100grade A
Adoption
Growing
2 stars
Reviews
Write oneNobody has reviewed zzop yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
zzop tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-20 · 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 qualitylocal package, no credentials required12/15
- Maintenancelast push 20 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/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.
zzop: common questions
- Is zzop MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the zzop safety report
- Does zzop need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is zzop maintained?
- The last commit was 20 days ago (2026-08-31). The latest release is v0.34.0.
- What can I use instead of zzop?
- Servers from other publishers that do the same job: treg.to MCP server.
Alternatives to zzop
Same job from other publishers: the closest match first, then the best rated.
- treg.toOpenRouter for tools and data. Compare catalog providers and call them from one hosted MCP endpoint.not reviewedEstablishedA
