Report 01M77H38WWZR5DPMQGHXX5SKNP · static-2
3DAssets.dev MCP server: automated checks
What HostedMCP checked on 12 Nov 2026, 09:23 UTC. Every result links to the public source it came from, so you can check it yourself.
7 of 8 checks ran · 0 high findings · not a security audit
- Checked
- 12 Nov 2026, 09:23 UTC
- Commit
- —
- Package
- 3dassets-mcp · 1.0.0
- Methodology
- static-2
What to fix for a higher score
One check can earn more points. The next scan runs within a week, or right after the repository changes.
- Open source license (OSI) up to +10 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.
Origin
15 / 25 points- PassSource repository linked and reachable15 pts
- FindingOpen source license (OSI)10 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
10 / 10 points- PassCommit or release in the last year10 pts
Supply chain
25 / 25 points- PassPackage name not close to a popular package15 pts
- PassNo critical advisory in the package or its dependencies10 pts
Tool safety
20 / 20 points- Not checkedDestructive tools are labelled10 pts
- PassNo hidden instructions to the model20 pts
Endpoint
10 / 10 points- PassRemote endpoint uses HTTPS10 pts
Starting the package
Needs the network to startWe installed 3dassets-mcp 1.0.0 in an isolated container that could reach only the package registry, started it with no network and no credentials, and asked for its tools on 16 Nov 2026.
It tried to reach the internet while starting. With no network it did not answer.
What these checks do not cover
- Tools are listed but never called, and the server's 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.