Ask from your AI

Ask your AI which send did it.

One URL, a Google sign-in, and the AI you already use names the send behind a spike. It never writes to your workspace.

In Claude — claude.ai or the desktop app — open Customize → Connectors, click + then Add custom connector.
2
Name it, paste the URL, leave OAuth Client ID and Client Secret empty, then click Add.
The name
```
SpamSpike
```
The URL
```
https://app.spamspike.com/api/mcp
```
Click Connect and sign in with Google in the browser that opens, with the address you use here.

On a Team or Enterprise plan, an Owner adds it first under Organization settings → Connectors; you then click Connect.

Using Claude Code in the terminal instead?

Then askWhich send sat behind bramble.co's worst day in the last 30 published days?

Ask which send sat behind a spike, whether SPF or DKIM failed, what blocked messages, or whether a recorded fix helped. Every figure keeps its source and date; missing evidence stays unknown.

What it can read

The sign-in is the door: it opens for a licensed address. Keys for a machine without a browser are created in the app, under Settings → Ask from your AI.