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.

Rexity Website-Check

REMOTE · WWW.REXITY.AI

Checks a public website in six areas and returns scores from 0 to 100. Free, no key needed.

Available components

+3 this week 87 Trust /100

Last scanned (3 hours ago)

Scores higher than 94% of remote servers

Reachable. Last reached 5 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 Security83
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 619 tokens (~619/item across 1 items; 1 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 3 Nov 26 +1

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

  • 1 Nov 26 +1

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

  • 29 Oct 26 +1

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

  • 27 Oct 26 +1

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

  • 25 Oct 26 +1

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

  • 23 Oct 26 +1

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

  • 21 Oct 26 +1

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

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 5 Nov 2026 · Probed https://www.rexity.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.rexity.ai CN=YR1,O=Let's Encrypt,C=US 22 Oct 2026 20 Jan 2027 RSA 2048 SHA256-RSA 658abaef1594d342440695eba2cf094e0f6
SANs: www.rexity.ai
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of www.rexity.ai. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
rexity.ai. present 23696 13 Verified
www.rexity.ai. Verified address RRset verified with the apex keys
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=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'self'; img-src 'self' data: blob: https:; font-src 'self' data:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; form-action 'self'; frame-src 'self' https://challenges.cloudflare.com
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.rexity.ai/mcp Verified 200
http (plaintext) http://www.rexity.ai/mcp HTTPS enforced 308 https://www.rexity.ai/mcp
MCP tools · 1 exposed · ~420 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
website_check ~420

Checks one public website and returns a short result as Markdown: an overall score (0–100) with a band (good / medium / weak), the scores of six areas (speed & technology, findability, readiness for enquiries, trust & legal, website security settings, e-mail domain protection), one verdict line per area, how many checks per area were met, partly met, open, notes or not checkable, a short verdict, the address and time of the check, and the source line. The single checks with their measured values are not part of this result: the full result is free on https://www.rexity.ai/website-check. Use it when a user asks how a specific public website performs for visitors, search engines and enquiries. It states what was measured and gives no advice. The areas on security settings and e-mail domain protection use only what is visible from outside (response headers, one TLS handshake, public DNS, security.txt): not a security audit, no warranty. Only public http/https websites on standard ports; IP addresses, internal hosts and sites whose owners opted out are refused with a message that says why. A fresh check takes up to about a minute; results are cached for 24 hours. Quotas for fresh checks, currently: 5 per IP address and day, 200 per hour and 1000 per day for all callers together; calls that arrive from the shared addresses of an assistant platform count together, 300 per day for the platform; when a quota is reached the result says when it is restored. Terms of use: https://www.rexity.ai/website-check/nutzung. The checker identifies itself as RexityWebsiteCheck/1.0 (+https://www.rexity.ai/website-check/bot).

NameTypeReqDescription
langstring–Language of the result: de (German, default) or en (English).
urlstringyesThe address of the website to check, for example www.example.de or https://www.example.de/. Public websites only.

No output schema declared.

No examples provided.

Install

How do I install the Rexity Website-Check MCP server?

Rexity Website-Check is a hosted endpoint at https://www.rexity.ai/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 · www.rexity.ai

# add to Claude Code
claude mcp add --transport http ai-rexity-website-check 'https://www.rexity.ai/mcp'
Common questions

What is the Rexity Website-Check MCP server?

Rexity Website-Check is an MCP server listed in the public MCP registry as ai.rexity/website-check. Checks a public website in six areas and returns scores from 0 to 100. Free, no key needed. This page covers its hosted endpoint (https://www.rexity.ai/mcp).

Is the Rexity Website-Check MCP server safe to use?

Rexity Website-Check scores 87 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 Rexity Website-Check MCP server expose?

Rexity Website-Check exposes 1 tool: website_check. Their descriptions and schemas cost roughly 420 tokens of context every time the server is loaded.

Does the Rexity Website-Check MCP server require authentication?

No. We connected to Rexity Website-Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Rexity Website-Check MCP server still maintained?

Rexity Website-Check is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.