Context Snipe
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_dependenciesA | List a project's resolved dependencies by parsing its lockfiles/manifests (Cargo.lock, package-lock.json, package.json, requirements.txt, go.mod/go.sum). Returns each dependency's name, version, and ecosystem. Use this to give the assistant ground-truth about exactly which packages and versions a project actually uses. |
| check_vulnerabilitiesA | Cross-reference a project's resolved dependencies against the OSV.dev vulnerability database and report which packages have known advisories (CVE/GHSA/RUSTSEC/PYSEC), with computed severity. Only reports advisories for packages actually present in the dependency tree — not generic noise. Requires network access to api.osv.dev. |
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 2 tools
The two tools have completely distinct purposes: one scans project dependencies and the other checks them against a vulnerability database. There is no overlap or ambiguity.
Both tools follow a clear verb_noun pattern: scan_dependencies and check_vulnerabilities, making the action and target immediately clear.
With only two tools, the server is minimal but well-scoped for its purpose. Each tool serves a necessary function, and the count is appropriate given the narrow focus.
The tool set covers the core workflow of listing dependencies and checking for known vulnerabilities. Minor gaps exist, such as lacking ability to fetch detailed advisory information or take action on findings, but the basic functionality is complete.