Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Audit website checks

REMOTE · AUDIT.HUUTRAN.DEV

Free SEO, AI visibility (AI crawlers, llms.txt, JSON-LD) and security-header checks for any URL.

+4 this week 75 Trust /100

Last scanned (22 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

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 Security74
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 993 tokens (~165/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 1.0.2 → 1.0.3 functional
  • 15 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “bulk_check” rewrote its description, which is the text the model reads security
    • Tool “compare_competitors” rewrote its description, which is the text the model reads security
    • Tool “full_site_crawl” rewrote its description, which is the text the model reads security
  • 13 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “bulk_check” rewrote its description, which is the text the model reads security
    • Tool “compare_competitors” rewrote its description, which is the text the model reads security
    • Tool “full_site_crawl” rewrote its description, which is the text the model reads security
    • Tool “ai_visibility_check” rewrote its description, which is the text the model reads security
    • Schema quality: 148 → 165 ▼ functional
    • Schema quality: 148 → 167 ▼ functional
    • Server version: 1.0.0 → 1.0.2 functional
  • 11 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 10 Nov 26 70

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://audit.huutran.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=audit.huutran.dev CN=WE1,O=Google Trust Services,C=US 2 Nov 2026 31 Jan 2027 ECDSA 256 ECDSA-SHA256 9b173a50ecdbcba9135fc3f13011c23a
SANs: audit.huutran.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of audit.huutran.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
huutran.dev. No DS 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
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://audit.huutran.dev/mcp Verified 200
http (plaintext) http://audit.huutran.dev/mcp HTTPS enforced 301 https://audit.huutran.dev/mcp
MCP tools · 6 exposed · ~807 tokens

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 →

Tool Tokens
ai_visibility_check ~262

Checks whether AI crawlers and AI search tools (ChatGPT, Claude, Perplexity, Google AI Overviews, Copilot) can read and cite a public URL: robots.txt rules for GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, PerplexityBot, Google-Extended, CCBot, Applebot-Extended and Bytespider; text and H1 in the raw server HTML; llms.txt and llms-full.txt; JSON-LD types; title, description, Open Graph, canonical, sitemap; nosnippet/noindex; and agent readiness: loads the page with the User-Agents of OAI-SearchBot, ChatGPT-User, Claude-SearchBot, PerplexityBot, GPTBot and ClaudeBot to catch firewall/CDN blocks robots.txt doesn't show, Content Signals, Link headers, Markdown negotiation (Accept: text/markdown), WebMCP forms and registerTool calls, and MCP server card, AI catalog and API catalog discovery. Passive GETs of public URLs only. Returns a 0-100 score and fixes.

NameTypeReqDescription
urlstringyesPublic web page to check, e.g. example.com or https://example.com/pricing

No output schema declared.

No examples provided.

bulk_check ~78

Quick on-page check of up to 10 URLs in one call: HTTP status, title, meta description, H1, canonical, noindex, lang, Open Graph and thin content. Needs Audit Pro ($15 per 3 months): https://audit.huutran.dev/mcp-server#pro

NameTypeReqDescription
urlsarrayyesPublic URLs

No output schema declared.

No examples provided.

compare_competitors ~118

Side-by-side on-page, AI-crawler and security-header signals for your page and up to 3 competitor pages: response time, title and description length, H1, word count, JSON-LD types, llms.txt, AI crawlers blocked in robots.txt, security headers. No backlink or domain-authority metrics. Needs Audit Pro ($15 per 3 months): https://audit.huutran.dev/mcp-server#pro

NameTypeReqDescription
competitorsarrayyesCompetitor pages
urlstringyesYour page

No output schema declared.

No examples provided.

full_site_crawl ~126

Crawls up to 25 pages of a public site (from its XML sitemap, or homepage links) and checks each for title, meta description, H1, canonical, noindex, html lang, Open Graph, thin content and HTTP errors, plus site-wide duplicate titles and descriptions. Needs Audit Pro ($15 per 3 months): https://audit.huutran.dev/mcp-server#pro

NameTypeReqDescription
max_pagesinteger–Pages to check (1-25, default 10)
urlstringyesSite or homepage, e.g. example.com

No output schema declared.

No examples provided.

security_headers_check ~121

Passive security check of one public URL: one ordinary page load plus public DNS. Grades HTTPS, HSTS, Content-Security-Policy, clickjacking protection, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, version-leaking headers, cookie flags, SPF, DMARC, DKIM, CAA and DNSSEC from A to F, with a fix for each issue. Not a vulnerability scan.

NameTypeReqDescription
urlstringyesPublic web page to check, e.g. example.com or https://example.com/pricing

No output schema declared.

No examples provided.

seo_check ~102

On-page SEO check of one public URL: title, meta description, H1, canonical, Open Graph, lang, viewport, noindex, word count and empty JavaScript app shells, robots.txt, XML sitemap, HTTPS, server response time and HTML size. Returns a 0-100 score and a plain-English fix for each issue.

NameTypeReqDescription
urlstringyesPublic web page to check, e.g. example.com or https://example.com/pricing

No output schema declared.

No examples provided.

Install

How do I install the Audit website checks MCP server?

Audit website checks is a hosted endpoint at https://audit.huutran.dev/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 · audit.huutran.dev

# add to Claude Code
claude mcp add --transport http dev-huutran-audit-website-checks 'https://audit.huutran.dev/mcp'
Common questions

What is the Audit website checks MCP server?

Audit website checks is an MCP server listed in the public MCP registry as dev.huutran.audit/website-checks. Free SEO, AI visibility (AI crawlers, llms.txt, JSON-LD) and security-header checks for any URL. This page covers its hosted endpoint (https://audit.huutran.dev/mcp).

Is the Audit website checks MCP server safe to use?

Audit website checks scores 75 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 Audit website checks MCP server expose?

Audit website checks exposes 6 tools: seo_check, ai_visibility_check, security_headers_check, full_site_crawl, compare_competitors, bulk_check. Their descriptions and schemas cost roughly 807 tokens of context every time the server is loaded.

Does the Audit website checks MCP server require authentication?

No. We connected to Audit website checks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Audit website checks MCP server still maintained?

Audit website checks is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Audit website checks MCP server?

VerifyMCP ran 13 checks on Audit website checks, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.