REPORT 01M7BSWNP8Q2TRMNSVKWANHTSF · checks-v2
Transcodely MCP server: automated checks
What HostedMCP checked on 14 Nov 2026, 01:14 UTC. Every result links to the public source it came from, so you can check it yourself.
Not verified
75/100
6 of 11 checks ran · 0 high findings · not a security audit
- Checked
- 14 Nov 2026, 01:14 UTC
- Commit
- —
- Package
- hosted endpoint
- Methodology
- checks-v2
Origin
15 / 15 points- PassSource repository linked and reachable10 pts
transcodely/mcp is public and reachable
github.com/transcodely/mcp ↗ - Not checkedPackage names this repository as its source5 pts
- Not checkedBuild provenance (Sigstore attestation)10 pts
- Pass
Practices
5 / 5 points- PassCommit or release in the last year5 pts
Last commit or release 2026-11-02
github.com/transcodely/mcp ↗ - Not checkedOpenSSF Scorecard15 pts
Supply chain
not checked- Not checkedPackage name not close to a popular package10 pts
- Not checkedNo critical advisory in the package or its dependencies15 pts
Tool safety
20 / 20 points- PassNo hidden instructions to the model15 pts
20 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; a later release can differ.
- A pass is not a guarantee of safety. Give every server the narrowest token or role it needs.