Run Barrion scans from your AI assistant
Add one line to your MCP client config. Claude, Cursor, Codex and other assistants can then start passive security scans and read the results, over an OAuth connection. No API key in your config file.
Sign in once
The first tool call opens your browser to sign in to Barrion and approve the connection. The token is cached in ~/.mcp-auth, refreshed automatically, and tied to your account. Delete that folder to sign out.
Tools
| Tool | Scope | What it does |
|---|---|---|
| create_passive_scan | scan:create | Start a passive scan of a URL. Subject to your plan’s daily scan limit and per-domain rescan window, exactly like the dashboard. |
| get_latest_scan_by_domain | scan:read | Security score, risk level, and a count of findings by severity for a domain’s most recent scan. www and non-www are treated as one domain. |
| whoami | - | The signed-in Barrion account and the scopes it granted. |
What it can reach
- →OAuth 2.1 with PKCE. A browser sign-in, never a key pasted into a file.
- →Scoped, short-lived tokens. Limited to
scan:createandscan:read, and revocable from your account at any time. - →Audience-pinned. A token issued for the MCP endpoint cannot be replayed against the main Barrion API.
- →Passive scans only. No payloads, no brute forcing, no state changes. Safe to run against live production.
Requirements
Node.js 20.18.1 or newer, which npx uses to run the launcher. Passive scans run on every plan, including the free tier.
FAQ
Which AI assistants can connect?
Any MCP client. Claude Desktop, Claude Code, Cursor, Codex, opencode and Windsurf all read the same mcpServers config block and differ only in where that config file lives. If your assistant speaks the Model Context Protocol, it works.
Does my Barrion password go into a config file?
No. The only thing in your MCP config is the command npx -y @barrion/mcp. Authentication is a browser sign-in the launcher runs the first time you use a tool, using OAuth 2.1 with PKCE. The resulting token is short-lived, scoped, and cached under ~/.mcp-auth on your machine.
What can the assistant actually do once it is connected?
It gets three tools: create_passive_scan (start a passive scan of a URL), get_latest_scan_by_domain (read the most recent scan's score, risk level and findings for a domain), and whoami. It acts as your Barrion user and is bound by the same plan limits and per-domain rescan windows as the dashboard. It cannot reach anything else in your Barrion account.
Is running scans from an assistant safe for production?
Yes. These are passive scans: they observe TLS, headers, cookies, DNS and network surface without sending payloads, brute forcing, or changing state. They are safe to run against live production traffic. Active testing (SQL injection, access control, IDOR) is a separate, scoped Barrion AI pentest.
What are the requirements?
Node.js 20.18.1 or newer, which npx uses to run the launcher. Nothing else to install: npx fetches @barrion/mcp on first use and keeps it cached.
Wire up your assistant
Create a free account, add npx -y @barrion/mcp to your client, and scan from the chat.