SocketDev / SocketDev/socket-mcp
Add a tool to return not only the scores themselves but also the reason for any deductions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 137
- Forks
- 46
- Avg merge
- 37m
- Merged PRs (30d)
- 1
Description
The socket.dev website displays scores along with reasons for deductions (e.g., known malware, eval function usage), but this MCP server only provides scores for the given packages.
When an AI agent attempts to access the socket.dev site to verify deduction reasons, it receives a 403 error. This leaves the AI agent with no means whatsoever to check deduction reasons.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing MCP tools that retrieve package scores and the Socket.dev API integration. Determine whether deduction reasons are available through the integration, then define the tool response so it returns both scores and reasons; done means an AI agent can retrieve those reasons without accessing the website.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100