Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoHTTP port for hosted mode, default 3000. Setting this variable or passing --http starts the hosted HTTP mode instead of stdio.3000
PUBLIC_URLNoRequired only in hosted mode. Public HTTPS address of the server, e.g. https://cve.example.com.
NVD_API_KEYNoOptional API key that raises the NVD rate limit for the search_cves tool. Not required in either stdio or hosted mode.
TOKENS_FILENoOptional in hosted mode. Path to the file containing people's tokens. Defaults to tokens.json next to the app.tokens.json
CVE_AUTH_TOKENNoRequired only in hosted mode. Owner token for the hosted server, at least 24 characters.
OAUTH_CLIENTS_FILENoOptional in hosted mode. Path to the file containing registered OAuth clients. Defaults to oauth-clients.json next to the app.oauth-clients.json

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_cveA

Fetch the official CVE record from CVE.org (CVE Services API) by ID, e.g. CVE-2021-44228. Each result includes exploited (listed in CISA's Known Exploited Vulnerabilities = attacked in the wild now) and epss (FIRST probability of exploitation in the next 30 days, 0-1).

search_cvesA

Search recent CVEs by keyword (product, library, vendor) via the NVD API. Use to find new vulnerabilities affecting a stack, e.g. keyword 'laravel', days 30. Sorted most urgent first. Each result includes exploited (listed in CISA's Known Exploited Vulnerabilities = attacked in the wild now) and epss (FIRST probability of exploitation in the next 30 days, 0-1).

check_packageA

Check whether a specific package version has known vulnerabilities (CVE/GHSA, and malicious-package reports) via OSV.dev. Ecosystems: npm, Packagist, PyPI, Maven, Go, crates.io, NuGet, RubyGems, etc. Each result includes exploited (listed in CISA's Known Exploited Vulnerabilities = attacked in the wild now) and epss (FIRST probability of exploitation in the next 30 days, 0-1).

scan_lockfileA

Scan a project's dependencies for known vulnerabilities in one go: takes a composer.lock or package-lock.json, checks every installed package against OSV.dev (GitHub advisories, Packagist/npm advisories, malicious packages), and ranks findings most urgent first. Pass path (project folder or lockfile), or the lockfile text in content with filename. Each result includes exploited (listed in CISA's Known Exploited Vulnerabilities = attacked in the wild now) and epss (FIRST probability of exploitation in the next 30 days, 0-1).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct granularity and input: scan_lockfile handles whole lockfiles, check_package handles a single package/version, get_cve retrieves by CVE ID, and search_cves finds CVEs by keyword. The boundary between scan_lockfile and check_package is clearly explained by scope, preventing likely misselection.

Naming Consistency5/5

All names follow a consistent snake_case verb_noun pattern: scan_lockfile, get_cve, search_cves, check_package. The singular/plural variation between get_cve and search_cves reflects the object semantics rather than a naming inconsistency.

Tool Count5/5

Four tools are well-scoped for a focused CVE/vulnerability server, with each tool covering a distinct workflow: project scanning, individual package checking, CVE lookup, and keyword search. No tool feels redundant or trivial.

Completeness4/5

The surface covers the core lifecycle: scanning dependencies, checking a specific package, fetching a CVE, and searching recent CVEs. Minor gaps exist, such as no direct GHSA/advisory lookup by ID or bulk CVE listing, but agents can work around these using the provided tools.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues