Report 01M77DNCV2JJ9TC91VPFYM7KTX · static-2
Fixmap MCP server: automated checks
What HostedMCP checked on 12 Nov 2026, 08:23 UTC. Every result links to the public source it came from, so you can check it yourself.
Not verified
81/100
6 of 8 checks ran · 1 high finding · not a security audit
- Checked
- 12 Nov 2026, 08:23 UTC
- Commit
- —
- Package
- @aryam/fixmap · 0.9.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.
- Package name not close to a popular package up to +15 pts
The package name is one edit away from a popular package. If it is not a fork of that package, pick a more distinct name, and say in the README what the package is.
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
10 / 25 points- FindingPackage name not close to a popular package15 pts
@aryam/fixmap looks like finmap-mcp
How to fix: The package name is one edit away from a popular package. If it is not a fork of that package, pick a more distinct name, and say in the README what the package is.
- 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
not checked- Not checkedRemote endpoint uses HTTPS10 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.