Créavores AEO Audit
NPM · CREAVORES-AEO-MCP · SCANNED SEP 23
AEO / AI-search audit of any URL: direct answers, JSON-LD, llms.txt, E-E-A-T, AI citations.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 33 of 117 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability85
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 798 tokens (~99/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Créavores AEO Audit MCP server?
Créavores AEO Audit runs locally as an npm package, launched with npx -y creavores-aeo-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · creavores-aeo-mcp
claude mcp add tresor4k-creavores-aeo-mcp -- npx -y creavores-aeo-mcp
{
"mcpServers": {
"tresor4k-creavores-aeo-mcp": {
"command": "npx",
"args": [
"-y",
"creavores-aeo-mcp"
]
}
}
} {
"servers": {
"tresor4k-creavores-aeo-mcp": {
"command": "npx",
"args": [
"-y",
"creavores-aeo-mcp"
]
}
}
} codex mcp add tresor4k-creavores-aeo-mcp -- npx -y creavores-aeo-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tresor4k-creavores-aeo-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"creavores-aeo-mcp"
],
"enabled": true
}
}
} openclaw mcp add tresor4k-creavores-aeo-mcp --command npx --arg -y --arg creavores-aeo-mcp
mcp_servers:
tresor4k-creavores-aeo-mcp:
command: "npx"
args: ["-y", "creavores-aeo-mcp"] {
"McpServers": {
"tresor4k-creavores-aeo-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"creavores-aeo-mcp"
]
}
}
} assistant mcp add tresor4k-creavores-aeo-mcp -t stdio -c npx -a -y creavores-aeo-mcp
{
"mcpServers": {
"tresor4k-creavores-aeo-mcp": {
"command": "npx",
"args": [
"-y",
"creavores-aeo-mcp"
]
}
}
} 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.
- 20 Sept 26 67
First indexed and scored.
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 23 Sept 2026 · Analysed npm/creavores-aeo-mcp@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 117 packages
| Packages resolved | 117 |
|---|---|
| Deprecated | 1 |
| Stale | 33 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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_aeo ~106
Runs a full Answer Engine Optimization (AEO) audit on a URL: crawlability (30pts), content structure for AI extraction (35pts), and E-E-A-T trust signals (35pts), plus llms.txt and AI-bot access checks. Returns a 0-100 score, sub-scores, a verdict, and prioritized, actionable recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL of the page to audit, e.g. https://example.com/page |
No output schema declared.
No examples provided.
check_agentic_readiness ~115
Assesses how readable and navigable a page is for AI agents performing 'agentic browsing' (Claude, ChatGPT agents, Perplexity, etc.), not just traditional search crawlers. Checks: llms.txt compliance, heading structure sanity, image alt-text coverage, ARIA landmarks/labels, meta robots directives, and whether AI-specific crawlers are blocked in robots.txt. Aligned with Lighthouse's new Agentic Browsing audit category.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL of the page to check. |
No output schema declared.
No examples provided.
check_direct_answer ~84
Checks whether a page has a concise 40-60 word direct-answer paragraph right under the H1 — the single strongest citability signal for AI/answer engines (ChatGPT, Perplexity, Google AI Overviews). Returns the detected passage, its word count, and a pass/fail verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL of the page to check. |
No output schema declared.
No examples provided.
check_eeat_signals ~102
Checks Experience-Expertise-Authoritativeness-Trustworthiness (E-E-A-T) signals on a page: byline/author, publish/modified dates, source citations (external links), links to an About/Methodology page, and legal-notice/privacy links. These signals matter for YMYL topics and for AI engines assessing whether to trust and cite a source.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL of the page to check. |
No output schema declared.
No examples provided.
check_llms_txt ~98
Checks whether a domain publishes an llms.txt file and whether it follows the llmstxt.org specification: H1 title, optional blockquote summary, '## Section' headings, and Markdown link list items ('- [Title](URL): notes'). Returns existence, a 0-100 compliance score, and the extracted links.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain or base URL, e.g. example.com or https://example.com |
No output schema declared.
No examples provided.
compare_aeo ~81
Compares the AEO scores of 2 to 3 URLs side by side (e.g. your page vs. one or two competitors). Returns each URL's overall score, sub-scores, ranking, and the biggest gaps to close to beat the top-ranked one.
| Name | Type | Req | Description |
|---|---|---|---|
| urls | array | yes | 2 to 3 full URLs to compare. |
No output schema declared.
No examples provided.
extract_structured_data ~99
Extracts and validates all JSON-LD structured data on a page: parses every <script type="application/ld+json"> block, reports @type list, JSON parse errors, common schema.org mistakes (missing required fields), and confirms the data is present server-side in the raw HTML (not injected client-side via useEffect, which AI crawlers may not execute).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL of the page to inspect. |
No output schema declared.
No examples provided.
simulate_ai_citation ~113
Simulates how an AI answer engine (ChatGPT, Perplexity, AI Overviews) would extract a citable passage from a page. Scans paragraphs, list items, table rows, and FAQ answers, scores each for self-containedness (length, no dangling pronouns, presence of numbers/definitions), and returns the single most citable passage plus an explanation of why it would (or would not) be picked over the others.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL of the page to analyze. |
No output schema declared.
No examples provided.
What is the Créavores AEO Audit MCP server?
Créavores AEO Audit is an MCP server listed in the public MCP registry as io.github.tresor4k/creavores-aeo-mcp. AEO / AI-search audit of any URL: direct answers, JSON-LD, llms.txt, E-E-A-T, AI citations. This page covers its npm package (creavores-aeo-mcp).
Is the Créavores AEO Audit MCP server safe to use?
Créavores AEO Audit scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 September 2026. It declares no install or post-install scripts. 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 Créavores AEO Audit MCP server expose?
Créavores AEO Audit exposes 8 tools: audit_aeo, check_direct_answer, extract_structured_data, check_llms_txt, check_eeat_signals, and 3 more. Their descriptions and schemas cost roughly 798 tokens of context every time the server is loaded.
Is the Créavores AEO Audit MCP server still maintained?
Créavores AEO Audit is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Créavores AEO Audit MCP server under?
Créavores AEO Audit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.