Assay MCP Server
Policy-enforcing MCP proxy with portable evidence output.
A88/100grade A
Adoption
Growing
10 stars
Reviews
Write oneNobody has reviewed Assay MCP Server yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Assay MCP Server 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 qualitylocal package, no credentials required12/15
- Maintenancelast push 0 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.
Assay MCP Server: common questions
- Is Assay MCP Server safe?
- Yes, by our scan: it is graded A (88/100). Read the Assay MCP Server safety report
- Does Assay MCP Server need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Assay MCP Server maintained?
- The last commit was in the last day (2026-09-19). The latest release is v6.6.2.