Report 01M7BV1A4XFW21SFTM9MA1MEGM · checks-v2
Paypilot Ach Returns MCP server: automated checks
What HostedMCP checked on 14 Nov 2026, 01:34 UTC. Every result links to the public source it came from, so you can check it yourself.
8 of 11 checks ran · 1 high finding · not a security audit
- Checked
- 14 Nov 2026, 01:34 UTC
- Commit
- —
- Package
- paypilot-ach-returns-mcp · 0.1.1
- Methodology
- checks-v2
What to fix for a higher score
4 checks can earn more points. The next scan runs within a week, or right after the repository changes.
- Build provenance (Sigstore attestation) up to +10 pts
Publish with build provenance:
npm publish --provenancefrom GitHub Actions withid-token: write, or PyPI Trusted Publishing, which adds attestations. - Open source license (OSI) up to +5 pts
Add a LICENSE file with an OSI-approved license such as MIT or Apache-2.0, and name it in package.json or pyproject.toml.
- OpenSSF Scorecard up to +15 pts
Add the OpenSSF Scorecard action (
ossf/scorecard-action) to the repository and fix the weakest checks it lists, such as branch protection, pinned dependencies and token permissions. - No hidden instructions to the model up to +15 pts
Remove text the model would read as an order from tool descriptions and the README: phrases like "ignore previous instructions", IMPORTANT tags, requests to hide things from the user, paths to credential files, and hidden Unicode characters.
Origin
15 / 20 points- PassSource repository linked and reachable10 pts
ivansflowgit/paypilot is public and reachable
github.com/ivansflowgit/paypilot ↗ - PassPackage names this repository as its source5 pts
paypilot-ach-returns-mcp name ivansflowgit/paypilot as source
pypi.org/project/paypilot-ach-returns-mcp/ ↗ - Not checkedBuild provenance (Sigstore attestation)10 pts
No build attestation published for this release
How to fix: Publish with build provenance:
npm publish --provenancefrom GitHub Actions withid-token: write, or PyPI Trusted Publishing, which adds attestations. - FindingOpen source license (OSI)5 pts
No license
How to fix: Add a LICENSE file with an OSI-approved license such as MIT or Apache-2.0, and name it in package.json or pyproject.toml.
Practices
5 / 5 points- PassCommit or release in the last year5 pts
Last commit or release 2026-11-12
github.com/ivansflowgit/paypilot ↗ - Not checkedOpenSSF Scorecard15 pts
How to fix: Add the OpenSSF Scorecard action (
ossf/scorecard-action) to the repository and fix the weakest checks it lists, such as branch protection, pinned dependencies and token permissions.
Supply chain
25 / 25 points- PassPackage name not close to a popular package10 pts
No popular package one edit away from paypilot-ach-returns-mcp
- PassNo critical advisory in the package or its dependencies15 pts
29 resolved dependencies checked; no critical advisory
osv.dev ↗
Tool safety
5 / 20 points- FindingNo hidden instructions to the model15 pts
Instruction aimed at the model found in the description or README
How to fix: Remove text the model would read as an order from tool descriptions and the README: phrases like "ignore previous instructions", IMPORTANT tags, requests to hide things from the user, paths to credential files, and hidden Unicode characters.
- PassDestructive tools are labelled5 pts
No tool named like delete, drop or exec
Endpoint
not checked- Not checkedRemote endpoint answers the MCP handshake5 pts
What these checks do not cover
- The server's code is not run and its logic is not audited.
- Results describe the repository and package on the date above; a later release can differ.
- A pass is not a guarantee of safety. Give every server the narrowest token or role it needs.