Skip to main content
Glama
offsec-mcp

offsec-mcp

by nadirzhon

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NVD_API_KEYNoOptional NVD API key to raise rate limits.
OFFSEC_SCOPENoInline authorization scope: comma-separated domains, wildcards, and CIDRs. Example: example.com,*.staging.example.com,10.0.0.0/24
OFFSEC_ALLOW_ANYNoSet to '1' to disable the authorization scope guard (use only for fully-owned lab).
OFFSEC_SCOPE_FILENoPath to a file containing authorization scope entries, one per line (# comments allowed).

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
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
recon_subdomainsA

Passively enumerate sub-domains of a domain from Certificate Transparency logs.

dns_lookupB

Resolve A/AAAA/MX/NS/TXT/CNAME records for a domain (via DNS-over-HTTPS).

whoisB

Look up domain registration data (registrar, dates, nameservers) via RDAP.

cve_searchB

Search the NVD for recent CVEs by keyword, filtered by minimum CVSS score.

cve_lookupB

Fetch full details and references for a specific CVE id (e.g. CVE-2024-3094).

analyze_jsB

Extract secrets, endpoints, and parameters from JavaScript (pasted content or a URL).

http_probeB

Fetch a URL and report status, key headers, and detected technologies. [active — needs scope]

security_headersB

Audit a site's HTTP security headers and grade them A–F. [active — needs scope]

port_scanB

TCP-connect scan a host for open ports (defaults to common ports). [active — needs scope]

scope_statusB

Report whether an authorization scope is configured for active tools.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 10 tools

Disambiguation4/5

Most tools have clearly distinct targets: DNS, WHOIS, subdomain enumeration, CVE search/detail, JS analysis, HTTP probing, header auditing, and port scanning. The main potential confusion is between cve_search and cve_lookup, and between http_probe and security_headers, but descriptions make the boundaries reasonably clear.

Naming Consistency3/5

The set mixes conventions: noun_verb forms like dns_lookup, cve_search, and port_scan alongside verb_noun analyze_js, bare nouns like whois and security_headers, and the less predictable recon_subdomains. The names are readable, but there is no single consistent pattern.

Tool Count5/5

Ten tools is well-scoped for an offensive-security reconnaissance server. Each tool maps to a distinct phase or resource, and none appears redundant or trivial.

Completeness4/5

The surface covers a solid recon workflow: subdomain discovery, DNS, WHOIS, CVE research, JavaScript analysis, HTTP probing, security-header auditing, and port scanning, plus scope status. Minor gaps exist, such as URL/content discovery or broader vulnerability scanning, but core workflows are represented.

Maintenance

ActivityInactive
ResponsivenessNo recent community issues