feat(web-security): add SecurityContext MCP server#69
Merged
Conversation
Add stdio proxy for the SecurityContext remote MCP service (https://securitycontext.dev/mcp) which provides repo-level vulnerability context mined from commit history and CVEs. Tools exposed: - get_security_context: hunting brief, top risks, variant leads - create_security_context: build/refresh context for a repo - get_vulnerability_leads: ranked lead backlog with severity filter The proxy handles the Streamable HTTP handshake internally and exposes tools over stdio, matching the pattern of all other MCP servers in the capability.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the SecurityContext MCP server to the web-security capability. SecurityContext mines a repo's commit history and disclosed CVEs to produce a hunting brief, top risks, and ranked variant leads — the context an agent needs before auditing a codebase.
What changed
mcp/securitycontext.py— Stdio proxy that handles the Streamable HTTP handshake withsecuritycontext.dev/mcpand exposes three tools:get_security_context— hunting brief, top risks, variant lead previewcreate_security_context— build/refresh context for a repoget_vulnerability_leads— full ranked lead backlog with severity/limit filterscapability.yaml— NewsecuritycontextMCP server entry (stdio, same pattern as all others). Supports optionalSECURITYCONTEXT_API_KEYenv var for Neo/private repos.Why a stdio proxy?
The remote server uses Streamable HTTP transport. The Dreadnode runtime's streamable-http client and SecurityContext disagree on content-type negotiation (
application/jsonvstext/event-streamon initialize). The stdio proxy sidesteps this cleanly and matches the pattern of every other working MCP server in the capability.Testing
Verified end-to-end in the TUI:
/reload→securitycontext ✓ connected · stdio · 3 toolsget_security_context("vercel/next.js")returns full context (73 fixed issues, 51 CVEs, 1072 variant leads)