Purchase Requisition MCP server
Reusable purchase-requisitions and dated runs of them: pass, fail, not applicable, and a sign-off.
B70/100grade B
Adoption
New
0 stars
Reviews
Write oneNobody has reviewed Purchase Requisition yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Purchase Requisition 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 scanremote-only server, no package to scann/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 qualityno auth information5/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 70/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.
Purchase Requisition: common questions
- Is Purchase Requisition MCP server safe?
- Mostly: it is graded B (70/100). Read the Purchase Requisition safety report
- Does Purchase Requisition need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Purchase Requisition maintained?
- The last commit was in the last day (2026-09-20). The latest release is v0.22.0.