AstraVerify inside your AI assistant

Last updated 2026-10-04

One server, every assistant

AstraVerify runs a remote MCP server at https://astraverify.com/mcp. In Claude you do not need that URL at all — AstraVerify is published in Claude’s connector directory, so you add it in one click. Any other assistant that supports the Model Context Protocol can call the URL directly: ChatGPT (connectors and the Apps SDK), Gemini (app, CLI and Enterprise), Cursor, Windsurf and others. Nothing to install on your side; no key is needed for cached results and a modest number of fresh scans.

Tools: check_email_security, check_discoverability, get_report, fetch_as_crawler and verify_fix. Scores are computed by the same rules as this website, so what your assistant says matches what the report page shows.

Claude — in the connector directory

AstraVerify is published in Claude’s connector directory, so there is nothing to paste and no URL to get right.

  • claude.ai: Settings → Connectors → Browse connectors → search AstraVerify → Connect. No authentication needed.
  • Claude Code: claude mcp add --transport http astraverify https://astraverify.com/mcp
  • Already added it as a custom connector by URL? That keeps working — there is no need to switch.
  • Then ask: "Is yourdomain.com set up right for email and AI discovery?"

ChatGPT

  • Connectors (Team/Enterprise/Pro with developer mode): Settings → Connectors → Create → MCP server URL https://astraverify.com/mcp, authentication none.
  • An AstraVerify app was submitted to OpenAI on 24 September 2026 and is awaiting review; OpenAI publishes no timeline. Until it is listed, add the server URL above. (OpenAI is retiring custom GPTs, so there is no Custom GPT route.)

Gemini

  • Gemini app (personal Google account): gemini.google.com → Settings → Connected apps → Custom apps → Add a custom app → URL https://astraverify.com/mcp → Next. No credentials are needed. Google limits custom apps to personal accounts (not Workspace accounts) in the US.
  • Antigravity / Gemini CLI: add {"mcpServers":{"astraverify":{"httpUrl":"https://astraverify.com/mcp"}}} to the CLI settings (~/.gemini/settings.json).
  • Gemini Enterprise: an admin registers the MCP server URL as a tool.

Registries

For clients that install from a registry rather than a URL, AstraVerify is published as com.astraverify/domain-trust in the official MCP Registry, and listed on Smithery, Glama and mcp.so. Each points at the same server as the URL above.

Plain HTTP

The same operations are available as JSON over HTTPS, described by https://astraverify.com/openapi.json:

curl "https://astraverify.com/api/v1/report?domain=yourdomain.com"
curl "https://astraverify.com/api/v1/fetch-as?domain=yourdomain.com&agent=gptbot"

Limits and keys

Results are cached for 15 minutes and served to everyone; a fresh scan costs real requests to the domain, so anonymous clients get a modest hourly allowance and each domain is scanned fresh at most 30 times an hour across all users. An AstraVerify API key (created on your page at /my, which you receive after any purchase) lifts the anonymous allowance. Send it as Authorization: Bearer av_….

The server is stateless and read-only except verify_fix, which re-fetches public pages. It never receives credentials and never writes to your domain.