Contract Clause Library Assemble MCP server
Assemble a contract from a searchable clause library, with variables filled in or flagged as missing
C65/100grade C
Adoption
New
0 stars
Reviews
Write oneNobody has reviewed Contract Clause Library Assemble yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Contract Clause Library Assemble tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.7 · 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 identitynamespace and repository owner differ; GitHub account older than a year5/10
Overall 65/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.
Contract Clause Library Assemble: common questions
- Is Contract Clause Library Assemble MCP server safe?
- With care: it is graded C, so read the findings first (65/100). Read the Contract Clause Library Assemble safety report
- Does Contract Clause Library Assemble need an API key?
- Yes. The registry entry asks for
MCP_LICENSE_KEY. - Is Contract Clause Library Assemble maintained?
- The last commit was in the last day (2026-09-19). The latest release is v0.21.0.