Reports MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REPORTS_JWT_TOKEN | Yes | Your JWT authentication token from your reports API system |
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 |
|---|---|
| update_reportB | Update a report. HTML fields (goal, scope, summary description/keyFindings, recommendations) use minimal HTML formatting: only tags for paragraphs and for simple bullet lists. NO nesting, NO numbered lists, NO code blocks, NO headers. |
| get_reportC | Retrieve a specific report by ID |
| get_all_reportsC | Retrieve all reports from the API |
| create_reportC | Create a new report |
| get_vulnerabilityC | Retrieve a specific vulnerability by ID |
| update_vulnerabilityC | Update a vulnerability. Use minimal HTML formatting: only tags for paragraphs and for simple bullet lists. NO nesting, NO numbered lists, NO code blocks, NO headers. |
| delete_vulnerabilityC | Delete a vulnerability by ID |
| get_vulnerabilitiesC | Retrieve all vulnerabilities for a specific report |
| create_vulnerabilitiesC | Create one or more vulnerabilities for a specific report. Use minimal HTML formatting: only tags for paragraphs and for simple bullet lists. NO nesting, NO numbered lists, NO code blocks, NO headers. |
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 9 tools
Each tool has a clearly distinct purpose targeting either reports or vulnerabilities with specific CRUD actions. For example, create_report vs. update_report, and get_vulnerabilities vs. get_vulnerability, with no overlap in functionality.
All tool names follow a consistent verb_noun pattern using snake_case, such as create_report, get_vulnerability, and update_vulnerability. There are no deviations in naming conventions across the set.
With 9 tools, the server is well-scoped for managing reports and vulnerabilities, covering essential CRUD operations for both entities. Each tool serves a clear purpose without redundancy or bloat.
The tool set provides complete CRUD coverage for both reports and vulnerabilities, including create, read, update, and delete operations. There are no obvious gaps, as all lifecycle stages are supported for the domain.