Socket MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP_MODE | No | Set to true to run the server in HTTP mode | |
| SOCKET_API_KEY | Yes | Your Socket API key with packages:list permission scope |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| depscoreA | Get the dependency score of packages with the |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools.
Single tool named 'depscore' is clear and concise; no inconsistency arises with only one tool.
With only one tool, the server feels underdeveloped for its stated purpose of dependency security, lacking features like package listing or alert management.
The single tool provides dependency scoring but misses other essential operations such as checking for known vulnerabilities, updating packages, or generating detailed reports, leaving significant gaps.