Report 01M78CJ5WTFSADNVNRRMZF2WXR · static-2
deadends.dev MCP server: automated checks
What HostedMCP checked on 12 Nov 2026, 17:23 UTC. Every result links to the public source it came from, so you can check it yourself.
8 of 8 checks ran · 0 high findings · not a security audit
- Checked
- 12 Nov 2026, 17:23 UTC
- Commit
- —
- Package
- deadends-dev · 0.9.0
- Methodology
- static-2
Origin
25 / 25 points- PassSource repository linked and reachable15 pts
- PassOpen source license (OSI)10 pts
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
30 / 30 points- PassDestructive tools are labelled10 pts
- PassNo hidden instructions to the model20 pts
Endpoint
10 / 10 points- PassRemote endpoint uses HTTPS10 pts
Starting the package
Listed its toolsWe installed deadends-dev 0.9.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 answered and listed its tools without any credentials. The list is below.
Tool definitions
Read by starting the package in an isolated container with no network and no credentials. Each new release is read again, and a definition that changes shows up here with the versions.
- Tools now
- 11
- Tracked since
- 16 Nov 2026
- Changes since then
- 0
- Version
- 0.9.0
- 16 Nov 2026First read11 tools recorded as the baseline0.9.0
Remote servers are read when they answer without sign-in or with a token from the maintainer; packages are started in an isolated container. Definitions are third-party text, shown as written.
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.