Ghost Security MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GHOST_SECURITY_API_KEY | Yes | Your Ghost Security API key (required). | |
| GHOST_SECURITY_REPO_ID | No | Optional repository ID to scope operations. | |
| GHOST_SECURITY_BASE_URL | No | Base URL for the Ghost Security API (default: https://api.ghostsecurity.ai/v2). |
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 |
|---|---|
| ghostsecurity_get_findingsB | Get security findings with optional filtering and pagination |
| ghostsecurity_count_findingsB | Get count and statistics of security findings |
| ghostsecurity_get_findingA | Get a specific security finding by ID (requires repository and project context) |
| ghostsecurity_update_findingA | Update a security finding (status and/or comments). At least one of status or comments must be provided. |
| ghostsecurity_get_repositoriesB | Get repositories with optional filtering and pagination |
| ghostsecurity_get_repositoryA | Get a specific repository by ID |
| ghostsecurity_get_repository_findingsC | Get security findings for a specific repository |
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
Each tool targets a distinct operation: counting, retrieving specific findings, filtering findings, retrieving repositories, retrieving a specific repository, repository-scoped findings, and updating findings. No overlapping purposes exist.
All tools follow a consistent 'ghostsecurity_verb_noun' pattern (e.g., ghostsecurity_get_findings, ghostsecurity_update_finding). The naming is predictable and uniform.
7 tools is well-scoped for a security findings server, covering essential read and limited write operations without being excessive or insufficient.
The tool surface covers core functionality (CRUD for findings, read for repositories) but lacks operations like creating or deleting findings, which may be intentional given typical security workflows.