AstraVerify Domain Trust Check

Re-check one discoverability area after a fix

verify_fix

Read-onlyIdempotent

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.

Input Schema

Name	Required	Description	Default
`domain`	Yes	The domain to check, as the person gave it (no scheme, no path). Reserved names such as example.com are refused.
`component`	Yes

Output Schema

Name	Required	Description
`cdn`	No
`raw`	No	What the components add up to, before the cap
`grade`	Yes	A+ to F, or null alongside a null score
`score`	Yes	Out of 100, exactly as astraverify.com shows it. Null when not_applicable or inconclusive is set.
`capped`	No
`domain`	Yes
`reason`	No	Why score is null, when it is
`verdict`	No	One sentence on what engines can do with the site
`held_back`	No	Points the cap holds back while a fix is open (89 cap) or a critical one is (69). Not taken from any component: sum(components.points) - held_back = score
`components`	No
`open_fixes`	No	Findings above info level
`report_url`	No	The report page for this domain on astraverify.com
`request_id`	No	req_... for this call. Quote it when reporting a problem with the result.
`website_at`	No	When the domain asked about serves no website but its registrable domain does, that domain's discoverability result. The score belongs to `domain` here, not to the domain in the request.
`not_checked`	No	Parts skipped in this scan
`inconclusive`	No	The site could not be fetched, so the scan could not be completed. A failure to measure, not a finding about the site.
`canonical_host`	No
`not_applicable`	No	The domain publishes no web address, so there is no website to assess. Not a low score: score and grade are null and there are no recommendations. verdict names the domain to scan instead.
`recommendations`	No
`cache_age_seconds`	No	Age of the result; 0 means it was scanned just now
`verified_component`	No	Set by verify_fix: the component re-checked

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 9, 2026

addedOutput schema / properties / website_at / properties / components

Added value: +{
+  "description": "Component headlines only; scan this domain for the checks behind them",
+  "items": {
+    "properties": {
+      "key": {
+        "type": "string"
+      },
+      "max": {
+        "type": "integer"
+      },
+      "name": {
+        "type": "string"
+      },
+      "points": {
+        "type": "integer"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / website_at / properties / report_url
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedOct 9, 2026

addedOutput schema / properties / website_at

Added value: +{
+  "description": "When the domain asked about serves no website but its registrable domain does, that domain's discoverability result. The score belongs to `domain` here, not to the domain in the request.",
+  "properties": {
+    "cache_age_seconds": {
+      "type": "integer"
+    },
+    "domain": {
+      "type": "string"
+    },
+    "grade": {
+      "type": "string"
+    },
+    "open_fixes": {
+      "type": "integer"
+    },
+    "score": {
+      "type": "integer"
+    },
+    "verdict": {
+      "type": "string"
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}

Changed1 schema field changedSep 27, 2026

addedOutput schema / properties / request_id

Added value: +{
+  "description": "req_... for this call. Quote it when reporting a problem with the result.",
+  "type": "string"
+}

Changed2 schema fields changedSep 27, 2026

addedOutput schema / properties / held_back

Added value: +{
+  "description": "Points the cap holds back while a fix is open (89 cap) or a critical one is (69). Not taken from any component: sum(components.points) - held_back = score",
+  "type": "integer"
+}

changedOutput schema / properties / raw / description

Previous value: -"Before the cap rules that hold the headline back while a fix is open"New value: +"What the components add up to, before the cap"

Changed11 schema fields changedSep 26, 2026
- changedOutput schema / properties / canonical_host / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / cdn / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / recommendations / items / properties / fix / description
```
Previous value: -"The exact change to publish: a DNS record (name, type, value) or a file or tag (kind, label, value, where)"New value: +"The exact change to publish: a DNS record (name, type, value) or a file or tag (kind, label, value, where). Null when there is nothing to publish, for example \"turn on DKIM in your provider\"."
```
- changedOutput schema / properties / recommendations / items / properties / fix / properties / kind / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / recommendations / items / properties / fix / properties / label / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / recommendations / items / properties / fix / properties / name / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / recommendations / items / properties / fix / properties / note / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / recommendations / items / properties / fix / properties / type / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / recommendations / items / properties / fix / properties / value / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / recommendations / items / properties / fix / properties / where / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / recommendations / items / properties / fix / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```

Changed7 schema fields changedSep 26, 2026

changedOutput schema / properties / grade / description

Previous value: -"A+ to F"New value: +"A+ to F, or null alongside a null score"

changedOutput schema / properties / grade / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

addedOutput schema / properties / inconclusive

Added value: +{
+  "description": "The site could not be fetched, so the scan could not be completed. A failure to measure, not a finding about the site.",
+  "type": "boolean"
+}

addedOutput schema / properties / not_applicable

Added value: +{
+  "description": "The domain publishes no web address, so there is no website to assess. Not a low score: score and grade are null and there are no recommendations. verdict names the domain to scan instead.",
+  "type": "boolean"
+}

addedOutput schema / properties / reason

Added value: +{
+  "description": "Why score is null, when it is",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / properties / score / description

Previous value: -"Out of 100, exactly as astraverify.com shows it"New value: +"Out of 100, exactly as astraverify.com shows it. Null when not_applicable or inconclusive is set."

changedOutput schema / properties / score / type

Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]

Changed1 schema field changedSep 23, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "cache_age_seconds": {
+      "description": "Age of the result; 0 means it was scanned just now",
+      "type": "integer"
+    },
+    "canonical_host": {
+      "type": "string"
+    },
+    "capped": {
+      "type": "boolean"
+    },
+    "cdn": {
+      "type": "string"
+    },
+    "components": {
+      "items": {
+        "description": "One scored area of the domain",
+        "properties": {
+          "enabled": {
+            "type": "boolean"
+          },
+          "key": {
+            "type": "string"
+          },
+          "max": {
+            "type": "integer"
+          },
+          "name": {
+            "type": "string"
+          },
+          "points": {
+            "type": "integer"
+          },
+          "summary": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "key",
+          "name",
+          "points",
+          "max"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "domain": {
+      "type": "string"
+    },
+    "grade": {
+      "description": "A+ to F",
+      "type": "string"
+    },
+    "not_checked": {
+      "description": "Parts skipped in this scan",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "open_fixes": {
+      "description": "Findings above info level",
+      "type": "integer"
+    },
+    "raw": {
+      "description": "Before the cap rules that hold the headline back while a fix is open",
+      "type": "integer"
+    },
+    "recommendations": {
+      "items": {
+        "properties": {
+          "component": {
+            "type": "string"
+          },
+          "fix": {
+            "description": "The exact change to publish: a DNS record (name, type, value) or a file or tag (kind, label, value, where)",
+            "properties": {
+              "kind": {
+                "type": "string"
+              },
+              "label": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              },
+              "note": {
+                "type": "string"
+              },
+              "type": {
+                "type": "string"
+              },
+              "value": {
+                "type": "string"
+              },
+              "where": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "id": {
+            "type": "string"
+          },
+          "scan": {
+            "enum": [
+              "email",
+              "discoverability"
+            ],
+            "type": "string"
+          },
+          "severity": {
+            "enum": [
+              "critical",
+              "important",
+              "info"
+            ],
+            "type": "string"
+          },
+          "tags": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "title": {
+            "type": "string"
+          },
+          "why": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "severity",
+          "title"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "report_url": {
+      "description": "The report page for this domain on astraverify.com",
+      "type": "string"
+    },
+    "score": {
+      "description": "Out of 100, exactly as astraverify.com shows it",
+      "type": "integer"
+    },
+    "verdict": {
+      "description": "One sentence on what engines can do with the site",
+      "type": "string"
+    },
+    "verified_component": {
+      "description": "Set by verify_fix: the component re-checked",
+      "type": "string"
+    }
+  },
+  "required": [
+    "domain",
+    "score",
+    "grade"
+  ],
+  "type": "object"
+}

First observedSep 21, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/open-world/non-destructive, but the description adds behavior the annotations cannot: a NOT_READY result when there is no prior scan, a live re-fetch that is never cache-served, a shared budget of 30 scans/hour counted across all callers, and the reassurance that it only re-reads public pages and changes nothing. That is substantive operational context beyond the structured hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and precondition are front-loaded, and nearly every sentence carries distinct information (precondition, inputs, return, freshness rationale, budget, side effects). It runs long and the budget/cache sentences could be tightened, but there is little pure filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with an output schema, the description covers everything an agent needs: precondition, input format, failure mode (NOT_READY), freshness guarantee, quota impact, and side-effect safety. Nothing material is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% (only domain is documented in the schema), so the description compensates by explaining that domain is bare ('like example.com') and that component is 'the identifier from the earlier scan's findings' drawn from the enumerated list. It also conveys the cross-call dependency between component and the prior scan's findings, which the schema enum alone cannot express.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('re-check a single discoverability component') and scopes it to a post-fix re-verification, which cleanly separates it from the sibling check_discoverability that does the full scan. An agent can pick this apart from its siblings without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition ('use only once check_discoverability has reported that component failing and the person says the fix is done - never speculatively') and names the alternative for the other case ('use a full check_discoverability instead when several areas changed'). Both when-to-use and when-not-to-use are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AstraVerify Domain Trust Check tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?