GuardianMCP
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_vulnerabilitiesA | Scans project dependencies (package.json, composer.json) for known security vulnerabilities using the OSV.dev database. Supports multiple scan modes: 'full' for detailed reports, 'summary' for quick overview, 'critical-high-only' for auto-scans showing only actionable issues. Use this tool when: user asks about security/vulnerabilities, after package installations (npm install, composer update), before commits/builds, or when starting work in a new project with dependency files. |
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
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'check_vulnerabilities' has a clear, distinct purpose focused on security vulnerability scanning.
The tool name 'check_vulnerabilities' follows a consistent verb_noun pattern, and since there is only one tool, there is no inconsistency to evaluate. The naming is clear and appropriate for its function.
A single tool for a security vulnerability scanning server is too limited in scope. While the tool is well-described, a server with only one tool often feels thin and lacks the breadth needed for comprehensive security operations, such as managing scans, updating databases, or handling different file types beyond the mentioned ones.
The tool surface is severely incomplete for a security vulnerability domain. It only covers scanning for vulnerabilities in specific dependency files, missing essential operations like configuring scan settings, retrieving historical scan results, updating vulnerability databases, or integrating with other security tools. This creates significant gaps that could lead to agent failures in broader security workflows.