ROAS Expert free AI SEO audit
REMOTE · TOOLS.ROASEXPERT.COM
Free SEO and AI search readiness audit: score out of 100, platform detection, fixes per CMS.
Available components
Last scanned (23 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Marketing and SEO
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 Security77
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1217 tokens (~173/item across 7 items; 7 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 Management47
- Stability observed for 14 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 26 +1
- Schema quality: 1029 → 1217 ▼ functional
- New tool “check_ai_visibility” functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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 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.
- 28 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “explain_fix” rewrote its description, which is the text the model reads security
- Tool “get_report” rewrote its description, which is the text the model reads security
- Schema quality: 148 → 171 ▼ functional
- New tool “audit_product_page” functional
- “list_checks” reworded the description of “category” cosmetic
- 27 Oct 26 +8
- Authorization: unverified → partial ▲ security
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Probed https://tools.roasexpert.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tools.roasexpert.com | CN=WE1,O=Google Trust Services,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 7d4b5e27c466a0e60e101b3a813376da |
| SANs: tools.roasexpert.com | ||||||
| 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 secure
Validation of tools.roasexpert.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| roasexpert.com. | present | 63151 | 8 | Verified |
| tools.roasexpert.com. | 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 |
|---|---|
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src https://fonts.gstatic.com; img-src 'self' data: https:; connect-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tools.roasexpert.com/mcp | Verified | 200 | |
| http (plaintext) | http://tools.roasexpert.com/mcp | HTTPS enforced | 301 | https://tools.roasexpert.com/mcp |
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 →
audit_product_page Audit one product page for AI shopping readiness ~169
Runs the ROAS Expert product page check on one product URL and returns the score out of 100, the grade, the platform, category scores, the top three issues, the status of all 19 checks, a table of which questions a shopping assistant can answer from the page (price, stock, delivery, returns, variants, identity, ratings) and a shareable report link. The detail and the platform-specific fix for every failing or warning check are unlocked with the user's work email through unlock_report. Takes 5 to 15 seconds. Pass a product page URL; a homepage or other page gets a short note and does not count against the free limit, which is shared with audit_site.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Product page URL, for example https://store.com/products/example |
No output schema declared.
No examples provided.
audit_site Audit a website for SEO and AI search readiness ~134
Runs the free ROAS Expert audit on a public website and returns the score out of 100, the grade, the detected platform, category scores, the top three issues, the status of all 48 checks and a shareable report link. The detail and the platform-specific fix for every failing or warning check are unlocked with the user's work email through unlock_report. Takes 10 to 25 seconds. Use the domain or homepage URL, not a deep link. Free plan: a few audits per day per client.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Domain or homepage URL, for example example.com or https://www.example.com |
No output schema declared.
No examples provided.
check_ai_visibility Check how often AI assistants name a brand ~188
Asks ChatGPT, Perplexity, Claude and/or Gemini the user's buyer questions several times each (five runs per question on the free plan) and returns how often the brand is named, its average position, the range around the rate, the other brands named instead and the domains the answers cite, plus a report link. Takes 30 to 90 seconds. Counts against the free daily allowance. Pass one to five plain buying questions as a shopper would type them.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | Brand name as people write it, for example Acme Running |
| domain | string | – | Optional website, for example acmerunning.com, used to spot mentions by URL |
| models | array | – | Which assistants to ask; defaults to chatgpt |
| prompts | array | yes | One to five buyer questions, for example "Best running shoes for flat feet under $150?" |
No output schema declared.
No examples provided.
explain_fix Get the fix for a check on a given platform ~108
Returns the fix text for one check id (from list_checks, a site report or a product page report) written for a platform: shopify, wordpress, magento, framer, webflow, wix, squarespace, bigcommerce, hubspot, nextjs or generic. No usage limit.
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | string | yes | Check id, for example ai_bots, product_schema, llms_txt |
| platform | string | – | Platform key or CMS name; defaults to generic |
No output schema declared.
No examples provided.
get_report Fetch a stored audit report ~88
Returns a previously run audit by its id (the last part of a tools.roasexpert.com/r/<id> or /p/<id> link). Locked reports show the top three issues and check statuses; unlocked reports show every finding with its fix and the written summary. Reports are kept for 90 days. No usage limit.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Report id, 8 characters |
No output schema declared.
No examples provided.
list_checks List every check and its weight ~69
The catalogue of checks the audit runs, grouped by category with weights and a one-line description of what passes. Use it to explain a score or to see what the audit covers. No usage limit.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter; "product" lists the 19 product page checks |
No output schema declared.
No examples provided.
unlock_report Unlock the full report with a work email ~101
Unlocks a report: every failing and warning check with its detail and the fix written for the detected platform, plus the written summary. The email goes to ROAS Expert's CRM with the report link and gets at most one follow-up about the findings. Only call this with an email the user gave you for this purpose. No usage limit.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The user's work email address | |
| id | string | yes | Report id from audit_site |
No output schema declared.
No examples provided.
How do I install the ROAS Expert free AI SEO audit MCP server?
ROAS Expert free AI SEO audit is a hosted endpoint at https://tools.roasexpert.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.
remote · tools.roasexpert.com
claude mcp add --transport http com-roasexpert-tools-seo-audit 'https://tools.roasexpert.com/mcp'
What is the ROAS Expert free AI SEO audit MCP server?
ROAS Expert free AI SEO audit is an MCP server listed in the public MCP registry as com.roasexpert.tools/seo-audit. Free SEO and AI search readiness audit: score out of 100, platform detection, fixes per CMS. This page covers its hosted endpoint (https://tools.roasexpert.com/mcp).
Is the ROAS Expert free AI SEO audit MCP server safe to use?
ROAS Expert free AI SEO audit scores 77 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 ROAS Expert free AI SEO audit MCP server expose?
ROAS Expert free AI SEO audit exposes 7 tools: audit_site, audit_product_page, get_report, unlock_report, list_checks, and 2 more. Their descriptions and schemas cost roughly 857 tokens of context every time the server is loaded.
Does the ROAS Expert free AI SEO audit MCP server require authentication?
No. We connected to ROAS Expert free AI SEO audit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ROAS Expert free AI SEO audit MCP server still maintained?
ROAS Expert free AI SEO audit is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.