LABSCO SUMMARY
Findings scoped to a pull request is the shape that gets security into review rather than after it.
A security dashboard is something people visit after an incident. Findings addressable by PR and by file mean the question can be asked where the work is happening — during review, about the diff in front of you. That is the difference between a tool that reports and one that changes what ships.
What it is
DryRun Security's insights endpoint. They publish no tool list; the documented capabilities are recent security activity, findings scoped to a pull request or file, natural-language questions about posture, and their Code Security Intelligence trends.
What you get
- Summaries of recent security activity
- Findings queried per pull request or per file
- Natural-language questions about security posture
- Code Security Intelligence trends and agent status
Requirements
A bearer API key. MCP is included with the platform through API access keys, and sales is direct — there is no public price list.
Setup effort
Paste a URL with a key — add the endpoint to your client
USE CASES
01
Reviewing a pull request with security context
Ask for the findings on this PR rather than opening a separate dashboard.
02
Answering a posture question
Put the question in plain language instead of assembling a report.
03
Watching the trend
Read Code Security Intelligence trends and agent status from the same connection.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client that can reach a remote endpoint
- A bearer API key
INSTALLATION
Connect your client
Add the endpoint to your client.
Server setup
ENDPOINT URL
https://insights-mcp.dryrun.security/api/insights/mcpRequirements
- A bearer API key