Verify email in Goose
Goose calls MCP servers extensions. Add Qualisend as a remote extension and the agent can verify addresses and clean lists in any session.
- MCP endpoint
- https://app.qualisend.com/api/mcp
- Authentication
- Sign-in or API key
- Available on
- Every Goose install, CLI and desktop, on all platforms. No plan gating - Goose is free and open source, but you connect your own LLM provider and pay that provider for the model usage.
Connect it to Goose
You need a Qualisend account - the free plan includes 100 verification credits that never expire - and Goose itself. Steps checked against Block's documentation in September 2026.
- 1
Run the configurator
Choose Add Extension, then Remote Extension (Streamable HTTP). Some builds label it Streaming HTTP.
goose configure - 2
Fill in the details
Name it qualisend, paste the endpoint, type 300 at the timeout prompt (it has no default and will not accept an empty value), enter a description, then answer yes to "Would you like to add custom headers?" and add Authorization with the value Bearer plus your Qualisend API key.
https://app.qualisend.com/api/mcp - 3
Or use the desktop app
Open the sidebar -> Extensions -> Add custom extension, pick the Streamable HTTP type, fill in name, URL and headers, then Add.
- 4
Check it
Start a new session and run goose info -v in a terminal, or open the Extensions panel in the desktop app, to confirm the qualisend extension is there.
goose info -v
Sign-in or API key
Either. Supply an Authorization header with your Qualisend API key, or leave headers out and Goose negotiates a client and opens a browser for sign-in on first use.
Check that it worked
Ask "how many Qualisend credits do I have left?". A number back means you are connected - that tool is free, so it costs nothing to test.
Config file
~/.config/goose/config.yamlYAML, not JSON. On Windows: %APPDATA%\Block\goose\config\config.yaml.
extensions:
qualisend:
enabled: true
type: streamable_http
name: qualisend
uri: https://app.qualisend.com/api/mcp
headers:
Authorization: "Bearer ${QUALISEND_API_KEY}"
env_keys:
- QUALISEND_API_KEY
timeout: 300
bundled: false
description: Qualisend email verificationWorth knowing
- The transport value is streamable_http with an underscore, and the URL field is uri - not url. Both differ from every JSON-based client.
- SSE is gone. A legacy type: sse entry has to be migrated to streamable_http.
- timeout here is in seconds (300), unlike the Gemini CLI where it is milliseconds.
- Header substitution resolves against Goose's merged environment map - list the variable under env_keys or it will not expand.
- The config is global. There is no per-project config.yaml; use recipes if you need different tool sets.
What to ask once it is connected
There are no commands to learn. Ask in your own words and Goose picks the right tool - there are twelve, covering verification, sending-domain deliverability and blacklist checks.
What Goose can reach
Only the verification tools, scoped to the single workspace you connect. It cannot reach another customer's data, your billing, or any admin function, and it never sees how a check is performed - just the verdict and the score. Authentication is an explicit token in a request header, never a cookie, so there is no session for a malicious page to borrow. Revoke it from Goose or from your Qualisend dashboard at any time; sign-in access also expires on its own within an hour. Full detail is on the MCP documentation page.
Goose FAQ
Block's own reference: Goose extensions docs
Using something else?
It is the same endpoint everywhere. Pick your client:
Any other MCP-compatible client works too - Cline, JetBrains AI Assistant and the rest all take the same Streamable HTTP endpoint. The MCP documentation has the transport and authentication details.
Start free with 100 credits that never expire, then paste the endpoint.