# AstraVerify Domain Trust Check (remote · astraverify.com)

Email security and AI discoverability scores for any domain, with the exact record or tag to fix.

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `astraverify.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-astraverify-domain-trust/astraverify.md), [page](https://verifymcp.io/servers/com-astraverify-domain-trust/astraverify)

## Channel facts

- Endpoint: `https://astraverify.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 565 tokens (~113/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-astraverify-domain-trust 'https://astraverify.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-astraverify-domain-trust": {
      "url": "https://astraverify.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-astraverify-domain-trust": {
      "type": "http",
      "url": "https://astraverify.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-astraverify-domain-trust]
url = "https://astraverify.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-astraverify-domain-trust": {
      "type": "remote",
      "url": "https://astraverify.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-astraverify-domain-trust --url 'https://astraverify.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-astraverify-domain-trust:
    url: "https://astraverify.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-astraverify-domain-trust": {
      "Transport": "http",
      "Url": "https://astraverify.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-astraverify-domain-trust -t streamable-http -u 'https://astraverify.com/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 73, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 73, 0)

- [functional improvement] Tool “check_discoverability” now declares an output schema
- [functional improvement] Tool “check_email_security” now declares an output schema
- [functional improvement] Tool “fetch_as_crawler” now declares an output schema
- [functional improvement] Tool “get_report” now declares an output schema
- [functional improvement] Tool “verify_fix” now declares an output schema
- [functional] First check of Tool coverage: 100

### 2026-09-23 (score 73, +1)

- [security] Tool “get_report” rewrote its description, which is the text the model reads

### 2026-09-22 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-21 (score 72)

First indexed and scored.

## MCP tools (5)

### `check_email_security` (~81 tokens)

Check email security (MX, SPF, DKIM, DMARC)

Email Security score for a domain with the DNS records found and the exact records to publish for each fix.

Input parameters:

- `domain` (string, required): 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)

Output parameters:

- `cache_age_seconds` (integer): Age of the result; 0 means it was scanned just now
- `capped` (boolean)
- `components` (array)
- `domain` (string)
- `grade` (string): 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): Out of 100, exactly as astraverify.com shows it

### `check_discoverability` (~96 tokens)

Check discoverability (search and AI crawler readiness)

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.

Input parameters:

- `domain` (string, required): 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)

Output parameters:

- `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)
- `grade` (string): 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): 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

### `get_report` (~107 tokens)

Domain Trust report (both scores)

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.

Input parameters:

- `domain` (string, required): 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)

Output parameters:

- `discoverability` (object|null)
- `discoverability_cache_age_seconds` (integer|null)
- `discoverability_error` (string|null)
- `domain` (string)
- `email_cache_age_seconds` (integer)
- `email_security` (object)
- `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

### `fetch_as_crawler` (~96 tokens)

Fetch the root page as a named crawler

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.

Input parameters:

- `agent` (string, required)
- `domain` (string, required): The domain to check, as the person gave it (no scheme, no path). Reserved names such as example.com are refused.

Output parameters:

- `agent` (string)
- `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)
- `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)

### `verify_fix` (~73 tokens)

Re-check one discoverability area after a fix

Re-runs only the checks behind one component (crawl, plumbing, metadata, structured, answer) and returns the updated score.

Input parameters:

- `component` (string, required)
- `domain` (string, required): The domain to check, as the person gave it (no scheme, no path). Reserved names such as example.com are refused.

Output parameters:

- `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)
- `grade` (string): 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): 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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-astraverify-domain-trust/astraverify#diagnostics

## Score history

- 2026-09-25: 73
- 2026-09-24: 73
- 2026-09-23: 73
- 2026-09-22: 72
- 2026-09-21: 72

## Common questions

### 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.

## Links

- Remote endpoint: https://astraverify.com/mcp
- Website: https://astraverify.com/connect
- Changelog RSS feed: https://verifymcp.io/servers/com-astraverify-domain-trust/astraverify.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-astraverify-domain-trust/astraverify.json
- HTML version of this page: https://verifymcp.io/servers/com-astraverify-domain-trust/astraverify