AstraVerify Domain Trust Check
REMOTE · ASTRAVERIFY.COM · SCANNED SEP 25
Email security and AI discoverability scores for any domain, with the exact record or tag to fix.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 565 tokens (~113/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the AstraVerify Domain Trust Check MCP server?
AstraVerify Domain Trust Check is a hosted endpoint at https://astraverify.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · astraverify.com
claude mcp add --transport http com-astraverify-domain-trust 'https://astraverify.com/mcp'
{
"mcpServers": {
"com-astraverify-domain-trust": {
"url": "https://astraverify.com/mcp"
}
}
} {
"servers": {
"com-astraverify-domain-trust": {
"type": "http",
"url": "https://astraverify.com/mcp"
}
}
} [mcp_servers.com-astraverify-domain-trust] url = "https://astraverify.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-astraverify-domain-trust": {
"type": "remote",
"url": "https://astraverify.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-astraverify-domain-trust --url 'https://astraverify.com/mcp' --transport streamable-http
mcp_servers:
com-astraverify-domain-trust:
url: "https://astraverify.com/mcp" {
"McpServers": {
"com-astraverify-domain-trust": {
"Transport": "http",
"Url": "https://astraverify.com/mcp"
}
}
} assistant mcp add com-astraverify-domain-trust -t streamable-http -u 'https://astraverify.com/mcp'
{
"mcpServers": {
"com-astraverify-domain-trust": {
"type": "http",
"url": "https://astraverify.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Tool “check_discoverability” now declares an output schema ▲ functional
- Tool “check_email_security” now declares an output schema ▲ functional
- Tool “fetch_as_crawler” now declares an output schema ▲ functional
- Tool “get_report” now declares an output schema ▲ functional
- Tool “verify_fix” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- 23 Sept 26 +1
- Tool “get_report” rewrote its description, which is the text the model reads security
- 22 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 21 Sept 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://astraverify.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=astraverify.com | CN=YE1,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6848d59716f6b2c6fb58fa710f7892796e5 |
| SANs: *.astraverify.com, astraverify.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of astraverify.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| astraverify.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: https:; font-src 'self' https:; connect-src 'self' https:; frame-ancestors 'none'; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://astraverify.com/mcp | Verified | 200 | |
| http (plaintext) | http://astraverify.com/mcp | HTTPS enforced | 301 | https://astraverify.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_discoverability Check discoverability (search and AI crawler readiness) ~96
Discoverability score for a domain: crawl access, site plumbing, page metadata, structured data and answer-engine readiness, with the exact file or tag to fix for each finding.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to check, as the person gave it (no scheme, no path). Reserved names such as example.com are refused. |
| refresh | boolean | – | Force a fresh scan instead of the cached result (rate limited) |
| Name | Type | Req | Description |
|---|---|---|---|
| cache_age_seconds | integer | – | Age of the result; 0 means it was scanned just now |
| canonical_host | string | – | – |
| capped | boolean | – | – |
| cdn | string | – | – |
| components | array | – | – |
| domain | string | yes | – |
| grade | string | yes | A+ to F |
| not_checked | array | – | Parts skipped in this scan |
| open_fixes | integer | – | Findings above info level |
| raw | integer | – | Before the cap rules that hold the headline back while a fix is open |
| recommendations | array | – | – |
| report_url | string | – | The report page for this domain on astraverify.com |
| score | integer | yes | Out of 100, exactly as astraverify.com shows it |
| verdict | string | – | One sentence on what engines can do with the site |
| verified_component | string | – | Set by verify_fix: the component re-checked |
No examples provided.
check_email_security Check email security (MX, SPF, DKIM, DMARC) ~81
Email Security score for a domain with the DNS records found and the exact records to publish for each fix.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to check, as the person gave it (no scheme, no path). Reserved names such as example.com are refused. |
| refresh | boolean | – | Force a fresh scan instead of the cached result (rate limited) |
| Name | Type | Req | Description |
|---|---|---|---|
| cache_age_seconds | integer | – | Age of the result; 0 means it was scanned just now |
| capped | boolean | – | – |
| components | array | – | – |
| domain | string | yes | – |
| grade | string | yes | A+ to F |
| null_mx | boolean | – | The domain declares that it sends and receives no mail |
| open_fixes | integer | – | Findings above info level |
| provider | string | – | Mail provider detected from MX |
| raw | integer | – | Before the cap rules that hold the headline back while a fix is open |
| recommendations | array | – | – |
| records | object | – | DNS records found, keyed mx, spf, dkim, dmarc |
| report_url | string | – | The report page for this domain on astraverify.com |
| score | integer | yes | Out of 100, exactly as astraverify.com shows it |
No examples provided.
fetch_as_crawler Fetch the root page as a named crawler ~96
What Googlebot, Bingbot, OAI-SearchBot, PerplexityBot, ClaudeBot or GPTBot receive from the site: status, redirects, headers and extracted text. Shows CDN or firewall blocks that robots.txt cannot.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | – |
| domain | string | yes | The domain to check, as the person gave it (no scheme, no path). Reserved names such as example.com are refused. |
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | – |
| blocked | boolean | – | The response refused the crawler (403, 429 or similar) |
| chain | array | – | Redirect hops |
| challenge | boolean | – | A bot-challenge page rather than the site |
| content_type | string | – | – |
| domain | string | yes | – |
| error | string|null | – | – |
| extract | string | – | The text this crawler would index |
| final_url | string | – | – |
| headers | object | – | – |
| label | string | – | The crawler as its operator names it |
| ms | integer | – | – |
| status | integer|null | – | HTTP status the crawler received |
| title | string | – | – |
No examples provided.
get_report Domain Trust report (both scores) ~107
Both scores, the open fixes ranked by severity, and a saved report link (report_url) that opens the same findings without a rescan; share it as-is. Use this first for "is my domain set up right?" questions.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to check, as the person gave it (no scheme, no path). Reserved names such as example.com are refused. |
| refresh | boolean | – | Force a fresh scan instead of the cached result (rate limited) |
| Name | Type | Req | Description |
|---|---|---|---|
| discoverability | object|null | – | – |
| discoverability_cache_age_seconds | integer|null | – | – |
| discoverability_error | string|null | – | – |
| domain | string | yes | – |
| email_cache_age_seconds | integer | – | – |
| email_security | object | yes | – |
| live_url | string | – | The live page, which rescans when the result is stale |
| recommendations | array | – | Both scans, ranked by severity |
| report_url | string | – | Saved snapshot (/r/<id>) that opens without a rescan; safe to share |
No examples provided.
verify_fix Re-check one discoverability area after a fix ~73
Re-runs only the checks behind one component (crawl, plumbing, metadata, structured, answer) and returns the updated score.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | – |
| domain | string | yes | The domain to check, as the person gave it (no scheme, no path). Reserved names such as example.com are refused. |
| Name | Type | Req | Description |
|---|---|---|---|
| cache_age_seconds | integer | – | Age of the result; 0 means it was scanned just now |
| canonical_host | string | – | – |
| capped | boolean | – | – |
| cdn | string | – | – |
| components | array | – | – |
| domain | string | yes | – |
| grade | string | yes | A+ to F |
| not_checked | array | – | Parts skipped in this scan |
| open_fixes | integer | – | Findings above info level |
| raw | integer | – | Before the cap rules that hold the headline back while a fix is open |
| recommendations | array | – | – |
| report_url | string | – | The report page for this domain on astraverify.com |
| score | integer | yes | Out of 100, exactly as astraverify.com shows it |
| verdict | string | – | One sentence on what engines can do with the site |
| verified_component | string | – | Set by verify_fix: the component re-checked |
No examples provided.
What is the AstraVerify Domain Trust Check MCP server?
AstraVerify Domain Trust Check is an MCP server listed in the public MCP registry as com.astraverify/domain-trust. Email security and AI discoverability scores for any domain, with the exact record or tag to fix. This page covers its hosted endpoint (https://astraverify.com/mcp).
Is the AstraVerify Domain Trust Check MCP server safe to use?
AstraVerify Domain Trust Check scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AstraVerify Domain Trust Check MCP server expose?
AstraVerify Domain Trust Check exposes 5 tools: check_email_security, check_discoverability, get_report, fetch_as_crawler, verify_fix. Their descriptions and schemas cost roughly 453 tokens of context every time the server is loaded.
Does the AstraVerify Domain Trust Check MCP server require authentication?
No. We connected to AstraVerify Domain Trust Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AstraVerify Domain Trust Check MCP server still maintained?
AstraVerify Domain Trust Check is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.