AstraVerify Domain Trust Check
v1.0.1Email security and AI discoverability scores for any domain, with the exact record or tag to fix.
Endpoint health
online- Last checked
- 11/20/2026, 6:16:12 AM
- Latency
- 116 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.astraverify%2Fdomain-trust
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.astraverify/domain-trust": {
"url": "https://astraverify.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
5 shown · authentication unknown
Check discoverability (search and AI crawler readiness)
check_discoverability
Check whether search engines and AI assistants can crawl, read and quote this site. Use when the person asks about SEO basics, robots.txt, sitemaps, llms.txt, or whether Google, ChatGPT, Claude or Perplexity can see their site. Input: a bare domain like example.com. Returns a Discoverability score 0-100 broken into crawl access (25: robots.txt, plus what the edge actually serves to Googlebot, Bingbot, OAI-SearchBot, PerplexityBot, ClaudeBot and GPTBot), site plumbing (20: HTTPS, one canonical host, sitemap, real 404s), page metadata (20), structured data (20) and answer-engine readiness (15: llms.txt, a definitional opening, question-form headings). Every finding carries the exact file, tag or record to publish. It makes roughly 15 fetches over a few seconds - robots.txt, the sitemap, the root page, up to four pages listed in the sitemap, llms.txt, the preview image, one deliberately missing URL to see how 404s are handled, and the root page once as each of the six crawlers. It identifies itself as AstraVerifyBot, except on those six checks, where the point is to send the crawler's own user-agent. It fetches nothing off that domain and crawls no further. Cached 15 minutes. It changes nothing on the site. This is a separate scan from check_email_security and does not include it. It scores crawl access across all six crawlers at once; for the exact response a single named crawler receives - status, redirect chain, headers, the text it would index - use fetch_as_crawler.
Schema valid · SHA-256 0ea2a853b0cd…
View input schema
{ "type": "object", "properties": { "domain": { "description": "The domain to check, as the person gave it (no scheme, no path). Reserved names such as example.com are refused.", "maxLength": 253, "minLength": 3, "type": "string" }, "refresh": { "default": false, "description": "Force a fresh scan instead of the cached result (rate limited)", "type": "boolean" } }, "required": [ "domain" ] }
Connections
streamable-http
https://astraverify.com/mcp