Skip to main content
Glama
Sign In

AstraVerify Domain Trust Check

by com.astraverify
OverviewDiscussionsAdmin

Check discoverability (search and AI crawler readiness)

check_discoverability
Read-onlyIdempotent

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.

Input Schema

NameRequiredDescriptionDefault
domainYesThe domain to check, as the person gave it (no scheme, no path). Reserved names such as example.com are refused.
refreshNoForce a fresh scan instead of the cached result (rate limited)

Output Schema

NameRequiredDescriptionDefault
cdnNo
rawNoWhat the components add up to, before the cap
gradeYesA+ to F, or null alongside a null score
scoreYesOut of 100, exactly as astraverify.com shows it. Null when not_applicable or inconclusive is set.
cappedNo
domainYes
reasonNoWhy score is null, when it is
verdictNoOne sentence on what engines can do with the site
held_backNoPoints 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
componentsNo
open_fixesNoFindings above info level
report_urlNoThe report page for this domain on astraverify.com
request_idNoreq_... for this call. Quote it when reporting a problem with the result.
website_atNoWhen 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_checkedNoParts skipped in this scan
inconclusiveNoThe site could not be fetched, so the scan could not be completed. A failure to measure, not a finding about the site.
canonical_hostNo
not_applicableNoThe 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.
recommendationsNo
cache_age_secondsNoAge of the result; 0 means it was scanned just now
verified_componentNoSet by verify_fix: the component re-checked

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
+}
  2. Changed1 schema field changed
    • 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"
+  ]
+}
  3. Changed1 schema field changed
    • addedOutput schema / properties / request_id
      Added value: +{
+  "description": "req_... for this call. Quote it when reporting a problem with the result.",
+  "type": "string"
+}
  4. Changed2 schema fields changed
    • 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"
  5. Changed11 schema fields changed
    • 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"
+]
  6. Changed7 schema fields changed
    • 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"
+]
  7. Changed1 schema field changed
    • 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"
+}
  8. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description goes well beyond them: ~15 fetches over a few seconds, the exact resources fetched, self-identification as AstraVerifyBot except on the six crawler-impersonation checks, no off-domain fetches, no further crawling, 15-minute cache, and no site mutation. This is unusually rich disclosure of runtime behavior.

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 is front-loaded in the first sentence, and the operational detail (fetch plan, user-agent behavior, caching, sibling routing) is all decision-relevant rather than padding. The parenthetical scoring breakdown is dense and slightly long, but each clause maps to a distinct behavior an agent benefits from knowing.

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 read-only scan with a full annotation set and an output schema, the description covers the remaining gaps an agent needs: trigger conditions, scope boundaries, side-effect profile, runtime cost, caching, and the sibling routing rule for single-crawler queries. Nothing material is missing.

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 100%, so the schema already documents both parameters and the baseline is 3. The description adds format guidance beyond the schema ('Input: a bare domain like example.com') and the 'Cached 15 minutes' statement explains why the refresh flag exists. It stops short of naming the parameters explicitly, so it is not a 5.

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 and resource ('Check whether search engines and AI assistants can crawl, read and quote this site') and scopes it with the scoring breakdown (crawl access, plumbing, metadata, structured data, answer-engine readiness). It explicitly distinguishes itself from check_email_security ('a separate scan... does not include it') and fetch_as_crawler, so an agent can route correctly without opening either 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 explicit triggers ('Use when the person asks about SEO basics, robots.txt, sitemaps, llms.txt, or whether Google, ChatGPT, Claude or Perplexity can see their site') and names the alternative with the condition that selects it ('for the exact response a single named crawler receives... use fetch_as_crawler'). When-to-use, when-not-to-use, and the sibling boundary are all spelled out.

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 toolsInspect
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