Security Context MCP Server
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 |
|---|---|
| search_security_docsA | Search across security documentation from OWASP, NIST, AWS, Azure, Google, SANS, CIS, MITRE ATT&CK, and compliance frameworks (PCI DSS, HIPAA, ISO 27001, SOC 2, GDPR). Use natural language queries to find relevant security guidance, best practices, vulnerabilities, and controls. |
| get_security_contextC | Get comprehensive security context for a specific topic. Returns detailed information from multiple authoritative sources. |
| list_security_sourcesA | List all available security documentation sources and their categories |
| get_owasp_top10C | Get information about OWASP Top 10 vulnerabilities for a specific year or category |
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 4 tools
Each tool has a clearly distinct purpose with no overlap: get_owasp_top10 retrieves specific vulnerability data, get_security_context provides comprehensive topic analysis, list_security_sources enumerates available sources, and search_security_docs performs cross-source document searches. The descriptions clearly differentiate their functions, eliminating any potential for agent misselection.
All tool names follow a consistent verb_noun pattern with snake_case formatting: get_owasp_top10, get_security_context, list_security_sources, and search_security_docs. This predictable naming convention makes the tool set easy to understand and navigate for agents.
With 4 tools, the count is slightly lean but reasonable for a security context server focused on information retrieval. Each tool serves a distinct purpose, though the scope might benefit from additional tools for more granular operations like filtering or updating security data, but the current set is well-scoped for its core functions.
The tool set covers key retrieval operations for security context: listing sources, searching documents, getting specific vulnerability data, and obtaining comprehensive context. Minor gaps exist, such as the lack of tools for modifying or analyzing security data beyond retrieval, but agents can work around this to access authoritative security information effectively.