REPORT 01M7B83VM1VQK1SMBNWZPFDH96 · checks-v2
ParseAPI MCP server: automated checks
What HostedMCP checked on 13 Nov 2026, 20:03 UTC for parseapi-mcp 1.12.4. Every result links to the public source it came from, so you can check it yourself.
Passed HostedMCP checks v2
94/100
10 of 11 checks ran · 0 high findings · not a security audit
- Checked
- 13 Nov 2026, 20:03 UTC
- Commit
- —
- Package
- npm · 1.12.4
- Methodology
- checks-v2
Origin
25 / 30 points- PassSource repository linked and reachable10 pts
parseapi/mcp is public and reachable
github.com/parseapi/mcp ↗ - PassPackage names this repository as its source5 pts
parseapi-mcp names parseapi/mcp as source
npmjs.com/package/parseapi-mcp ↗ - PassBuild provenance (Sigstore attestation)10 pts
Sigstore attestation for parseapi-mcp
npmjs.com/package/parseapi-mcp/v/1.12.4#provenance ↗ - FindingOpen source license (OSI)5 pts
No license
Practices
5 / 5 points- Pass
- Not checkedOpenSSF Scorecard15 pts
Supply chain
25 / 25 points- PassPackage name not close to a popular package10 pts
No popular package one edit away from parseapi-mcp
- PassNo critical advisory in the package or its dependencies15 pts
8 resolved dependencies checked; no critical advisory
osv.dev ↗
Tool safety
20 / 20 points- PassNo hidden instructions to the model15 pts
13 tool descriptions and the README read; no override phrases, credential paths or hidden characters
- PassDestructive tools are labelled5 pts
No tool named like delete, drop or exec
Endpoint
5 / 5 points- PassRemote endpoint answers the MCP handshake5 pts
HTTPS endpoint answered 401 (sign-in required)
What these checks do not cover
- The server's code is not run and its logic is not audited.
- Results describe the state on the date above and parseapi-mcp 1.12.4; a later release can differ.
- A pass is not a guarantee of safety. Give every server the narrowest token or role it needs.