MCP Vulnerability Reporting
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_vulnerability_reportB | Create a professional vulnerability report following the standardized template format. IMPORTANT FOR AI - BE CONCISE AND BRIEF:
KEEP IT SHORT - Focus on key points only. No long paragraphs. |
| add_evidence_to_reportA | Add evidence (screenshots, requests, responses, PoC code) to an existing report |
| calculate_cvss_scoreB | Calculate CVSS score and vector for a report |
| export_reportA | Export vulnerability report as markdown file |
| list_reportsA | List all generated vulnerability reports |
| get_report_previewC | Get a preview of the generated markdown report |
| get_report_templateA | Get the report template format that should be followed. Use this to understand the exact structure and formatting requirements for vulnerability reports. |
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 7 tools
Most tools have distinct purposes, but get_report_preview and get_report_template could be confused as both relate to report formatting. Additionally, export_report and get_report_preview both produce markdown output, though one saves to file and the other displays inline.
All tool names follow a consistent snake_case verb_noun pattern (create, calculate, add, export, list, get, get). The pattern is predictable and readable, with no mixed conventions or vague verbs.
Seven tools is well-scoped for a vulnerability reporting server, covering creation, scoring, evidence, export, listing, preview, and template retrieval. Each tool serves a clear purpose without redundancy or bloat.
The tool surface lacks update and delete operations for reports, and while get_report_preview provides a partial retrieval, there is no full report getter. This creates notable lifecycle gaps, though add_evidence_to_report offers a limited update mechanism.