Integrations

Get findings where
your team works.

Connect a read-only DNS provider to discover zones and records, then route new findings and grade changes into the tools where your team works.

Start scanning freeBrowse DNS providersRead the Docs
250+
DNS provider connections
Read-only
No DNS changes
Verified
Before credentials save
Browse
Live provider catalog

Built-In Integrations

Six ways your findings reach you

Every new finding, grade change and scan completion can land exactly where you already work - or flow straight into your own systems through the public API.

Chat
Slack
Post new findings, grade drops and scan completions straight into a Slack channel your team already watches. Pick the channel from a live picker and send a test message before you trust it.
Chat
Microsoft Teams
The same real-time alerts, delivered as Adaptive Cards in a Teams channel. Connect with your Microsoft account - no bot install, no separate admin consent screen to chase down.
Two-way sync
Ticketing
Jira
Turn a critical finding into a Jira issue in one click, with the full remediation context attached. Resolve it in Jira and AYAsec picks up the status change automatically - no polling, no manual close-out.
Two-way sync
Ticketing
Linear
The same one-click ticket creation and automatic status sync, for teams that run on Linear instead of Jira. Inbound webhook is properly HMAC-signed, not a shared secret sitting in a URL.
Native
E-mail
No chat tool, no problem. Every alert can land directly in your inbox, the same way our scheduled-scan and grade-drop notifications already do - configurable per workspace.
Build your own
Public API & Webhooks
Everything above runs on the same token-authenticated, workspace-scoped API you can call yourself - with an interactive reference, sane rate limits, and outbound webhooks for wiring findings into anything that isn't listed here.

Not on the list? The public API and webhooks above expose the exact same findings, grades and scan events every integration on this page runs on - so you can wire AYAsec into anything that isn't here yet.

Read the API docs

Built For AI Assistants

Your AI assistant already speaks AYAsec.

AYAsec runs a hosted MCP (Model Context Protocol) server, so Claude Code, Claude Desktop, Cursor or any other MCP-compatible assistant can query your targets, scans, findings and alerts - or trigger a scan - using the exact same token you already use for the API. No separate OAuth flow, no new credential to manage.

  • Ask "which targets need attention across every client workspace" and get a real answer, grounded in your actual data
  • Every tool call re-checks the same scopes your token already has - the token is the entire safety boundary
  • One command to connect - no separate MCP credential, no extra setup screen
Read the MCP docsPro plan and above
claude mcp add --transport http ayasec \
  https://app.ayasec.ai/api/mcp \
  --header "Authorization: Bearer aya_..."

claude mcp list   # confirms it connected

Start Connecting

Connect your first integration in minutes

Create a free account, connect Slack, Teams, Jira or Linear from your workspace settings, and get your first routed alert on the next scan. No credit card, every integration included.

Create free accountRead the Docs