MCP Shamash
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHAMASH_AUDIT_LOG_PATH | No | Audit log location | ./audit.log |
| SHAMASH_MAX_TOKENS_PER_HOUR | No | Hourly token limit | 50000 |
| SHAMASH_MAX_TOKENS_PER_SCAN | No | Token limit per scan | 1000 |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_projectC | Performs comprehensive security scan on project directory |
| scan_networkC | Performs network scanning within project boundaries |
| pentest_applicationC | Performs penetration testing on deployed applications |
| check_complianceC | Validates project against compliance frameworks |
| generate_remediationC | Generate actionable remediation advice for findings |
| manage_false_positivesC | Manage false positive suppressions |
| manage_custom_rulesC | Manage custom security rules |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| security_review | Comprehensive security review prompt |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Scan Results | Access detailed scan results |
| Compliance Reports | Access compliance validation reports |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/NeoTecDigital/mcp_shamash'
If you have feedback or need assistance with the MCP directory API, please join our Discord server