What was blocked
The resource, directive, and policy mode. Your agent can see which rule a script, style, or request ran into.
Your visitors’ browsers report Content Security Policy violations. Warden collects those reports and gives your coding agents the context to investigate through MCP.
Start on the free plan. No card required.
Works with your favourite coding agents
A console error is a starting point. Warden groups related reports into issues your agents can explore, with the evidence kept together.
The resource, directive, and policy mode. Your agent can see which rule a script, style, or request ran into.
Affected pages, occurrence counts, and sanitised events. Enough context to trace an issue back to the code that needs attention.
Resolve an issue after fixing it. If another occurrence arrives, Warden reopens it with its history intact.
Send browser reports to Warden, then connect your agent through MCP to investigate in the tools you already use.
Create an endpoint, add your website’s hostnames, and copy the reporting header into your site. Start in report-only mode to collect violations without blocking resources.
Content-Security-Policy-Report-Only:
default-src 'self';
report-uri YOUR_ENDPOINT_URL;
report-to csp
Reporting-Endpoints:
csp="YOUR_ENDPOINT_URL"Replace YOUR_ENDPOINT_URL with the URL from your endpoint’s setup panel. This example observes violations without blocking resources.
Add Warden’s MCP URL to your compatible agent as a remote HTTP server. Sign in, choose your organisation, and authorise the connection.
https://app.cspwarden.com/api/mcpOnce reports arrive, ask your agent to explore them alongside your code. Here’s a question to start with:
Review my open CSP issues. Investigate the most frequent one and explain what I should check in my code.
Both plans collect your reports and connect to your agents. Choose Pro for more volume, longer history, and your whole team.
Something else on your mind?
Say hello
Yes. Free includes 10,000 reports per month, 1 reporting endpoint, 7-day event retention, and read-only MCP access for your agents. No card is required. You can upgrade to Pro when you need more capacity or team members.
Content Security Policy (CSP) is a browser security feature that lets your site specify which sources can load scripts, styles, images, and other resources. When something violates the policy, the browser can send a report. CSP Warden collects those reports and turns them into issues your agents can investigate through MCP.
Start with a Content-Security-Policy-Report-Only header. It asks browsers to report violations of that policy without blocking resources. Any enforced policy you already have still applies. Use what you learn to refine your policy before enforcing it.
No. CSP reporting is built into supporting browsers. Create an endpoint, allow your website’s hostnames, and configure your HTTP response headers. Delivery and reporting support vary by browser, so reports are useful evidence rather than a complete record of every visit.
A new occurrence after an issue was resolved automatically reopens it. Its history stays together so you can investigate the regression. You can also ignore issues that don’t need action.
On both Free and Pro, a compatible agent can read issues, sanitised events, and endpoints after you authorise access to your organisation. The MCP connection is read-only, so it cannot resolve issues or change your reporting configuration.
Free accepts 10,000 reports and Pro accepts 5,000,000 reports per UTC calendar month. Reports beyond the allowance are dropped until the next month; they are not queued for later. You can see your usage and limits in the dashboard.
Start on the Free plan, then upgrade to Pro in billing settings when you need higher limits or team access. Your paid subscription starts at checkout. You can manage or cancel it in billing settings. Monthly and yearly billing include the same features and report allowance.