AstraVerify Domain Trust Check 远程 MCP 服务器是什么?
AstraVerify Domain Trust Check 的远程 MCP 服务器是一个托管的 Model Context Protocol 端点,地址是 https://astraverify.com/mcp,AI 助手无需在本地安装或运行任何东西即可连接。
AstraVerify Domain Trust Check MCP Server已验证已精选
@AstraVerify
基本信息
关于 AstraVerify Domain Trust Check MCP Server
Email security and AI discoverability scores for any domain, with the exact DNS record or tag to fix. Five read-only tools, no account or key needed.
连接信息
https://astraverify.com/mcp接入方式
claude mcp add astraverify-domain-trust-check --transport http https://astraverify.com/mcpAstraVerify Domain Trust Check MCP Server 工具
5Check whether anyone can send email as this domain, and whether its own mail reaches the inbox. Use when the person asks about email security, spoofing or phishing risk, SPF, DKIM or DMARC setup, or why their mail goes to spam. Input: a bare domain like example.com - no scheme, no path. Given a URL or an email address, extract the domain and say what you extracted. Subdomains score in their own right: mail from the apex is not evidence about mail.example.com. Returns an Email Security score 0-100 broken into MX (25), SPF (25), DKIM (20) and DMARC (30), the status of each published record, the mail provider identified from MX, and the exact DNS record to publish for every finding. DNS-only, so it answers in about a second; cached 15 minutes, and refresh is for when DNS has just changed. One caveat to pass on rather than hide: DKIM selectors cannot be enumerated from DNS. They are found by probing the selectors known for the mail provider plus a list of a few hundred common names. A provider that issues random selectors - Amazon SES and Postmark among them - can only be confirmed from a live email, so report DKIM as not found by probing, never as proof the domain does not sign.
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.
Both AstraVerify scores for a domain, plus a shareable report link. Reach for this first on any broad question - "is my domain set up right?", "check my domain", "what should I fix first?" - and use the single-subject tools only once the person has narrowed it to email or to the website. Input: a bare domain like example.com. Returns the Email Security score, the Discoverability score, every open fix ranked critical then important then informational, and report_url. Work down that order. Some findings are marked as needing no action - a weak key the provider generates and the owner cannot replace, for instance - so do not present those as work. Unlike the other tools here, this one creates something: report_url is a snapshot of these findings saved to a new unlisted page at astraverify.com/r/..., and that page is what the person can send to whoever administers the domain. It opens later without rescanning, after the scan itself has aged out. Running the tool again on an unchanged scan returns the same page rather than a second one. Nothing is written anywhere the person owns. Set include_history to answer "has this improved?" or "did my fix land?": it adds the first and latest reading of each score, the move between them, and only the dates the score actually changed. A domain we have not watched before says so rather than reporting a flat line.
Show exactly what one named crawler receives from the domain's root page. Use when the person asks "what does Google see?" or "can ChatGPT read my site?", and whenever check_discoverability reports a crawl-access problem. check_discoverability scores crawl access across all six crawlers; this returns the one raw response behind that score, which is what explains such a result rather than restating it. robots.txt can read perfectly while a CDN or firewall returns 403 to one crawler and 200 to another, and only a real fetch shows that. Inputs: domain (bare, like example.com) and agent, exactly one of googlebot, bingbot, oai-searchbot, perplexitybot, claudebot, gptbot. Call it once per crawler to compare them. Returns the HTTP status, the full redirect chain, response headers, content type, the text that crawler would index, and flags for an outright block or a bot-challenge page - which is how cloaking becomes visible. One live fetch of the root page, nothing else, and it changes nothing.
Re-check a single discoverability component after the person has fixed it. Use only once check_discoverability has reported that component failing and the person says the fix is done - never speculatively. Without a previous scan to compare against it returns NOT_READY. Inputs: domain (bare, like example.com) and component, one of crawl, plumbing, metadata, structured, answer - the identifier from the earlier scan's findings. Returns that component re-measured and the updated Discoverability score, so you can tell the person plainly whether the change worked. Always a live re-fetch, never served from cache, which is exactly why it beats a second check_discoverability straight after an edit. It draws on the discoverability fresh-scan budget for that domain (30 an hour, counted across all callers), so use a full check_discoverability instead when several areas changed. It only re-reads public pages; it changes nothing on the site.
概览
What is AstraVerify Domain Trust Check
Ask your assistant about any domain and get two scores out of 100.
Email Security covers MX, SPF, DKIM and DMARC, including whether DMARC is actually enforced. Every finding comes with the exact TXT record to publish.
Discoverability covers what search engines and AI crawlers can get from the site: robots.txt rules for Googlebot, Bingbot, GPTBot, ClaudeBot, OAI-SearchBot and PerplexityBot, CDN blocks at the edge, the sitemap, www/apex redirects, canonical tags, titles and descriptions, Organization and WebSite structured data, llms.txt, and whether the opening paragraphs define the brand.
Tools
get_report: both scores, the open fixes ranked by severity, and the report link. Use this first for "is my domain set up right?" questions.check_email_security: MX, SPF, DKIM and DMARC findings with the exact records to publish.check_discoverability: crawl access, site plumbing, page metadata, structured data and answer-engine readiness.fetch_as_crawler: the exact HTTP status, redirects, headers and text a named crawler receives.verify_fix: re-checks one discoverability area after a change.
Setup
Streamable HTTP at https://astraverify.com/mcp. No account or key is needed. All tools are read-only: the server reads public DNS and public pages and writes nothing to your domain. Results are cached and shared; fresh scans are rate-limited per domain. An optional API key from https://astraverify.com/my raises the fresh-scan allowance for heavy users.
Scores match the report page at https://astraverify.com, so what the assistant says matches what the page shows.
Docs: https://astraverify.com/connect. Privacy: https://astraverify.com/privacy. Contact: hi@astraverify.com
常见问题
怎么连接 AstraVerify Domain Trust Check 的 MCP 服务器?
把端点 https://astraverify.com/mcp 添加到任意支持 MCP 的客户端,比如 Claude Code、Cursor 或 VS Code。本页的接入代码块可以一步配置好每个客户端。
AstraVerify Domain Trust Check 的 MCP 服务器需要认证吗?
不需要。AstraVerify Domain Trust Check 的 MCP 服务器不需要认证——直接用端点地址连接即可。
AstraVerify Domain Trust Check 的 MCP 服务器用的是哪种传输方式?
AstraVerify Domain Trust Check 暴露的是 Streamable HTTP 端点,这是远程 MCP 服务器普遍使用、主流客户端都支持的传输方式。
更多远程 MCP 服务器
AdaptlyPost
AdaptlyPost: Schedule and publish social posts to Instagram, TikTok, YouTube, X, Facebook, LinkedIn, Pinterest, Threads, and Bluesky from any MCP client.
%20-%20Sarah%20Xu.svg){kind=icon}
Adobe Marketing Agent
Marketing campaign and audience insights from Adobe
3
3GPP Scout
Hosted 3GPP MCP server: cited search across Rel-15 through Rel-20 TS/TR specs, recent TDocs, company proposals and meeting decisions. OAuth 2.1; no local index required.
AdWhispr - Research, Clone, & Launch Ads from Claude/ChatGPT
Remote MCP server that turns Claude, ChatGPT, or Cursor into a full ad workflow: research any brand's live Facebook and TikTok ads, clone the proven winners for your own brand, and launch real campaigns on Google, TikTok
A
Aayat AI
Pay-per-use data and tools for AI agents: crypto token safety and rug checks, web search with cited answers, page-to-Markdown, up-to-date library docs, package safety, company research and UK/EU open data. 160 tools, 20
评论