Créavores AEO Audit
NPM · CREAVORES-AEO-MCP
AEO audit of any URL + French open data: website prices, public tenders, editorial calendar.
Available components
Last scanned (20 hours ago)
Scores higher than 77% of npm servers
Category Marketing and SEO
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 114 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 39 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1396 tokens (~126/item across 11 items; 11 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 Nov 26 +1
- Stability: 0.97 → pass security
- 19 Nov 26 −1
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.97 functional
- 18 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 7 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.
- 5 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.
- 4 Nov 26 −3
- Stability: pass → 0.83 functional
- 2 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
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 · Analysed npm/creavores-aeo-mcp@1.1.0
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 114 packages
| Packages resolved | 114 |
|---|---|
| 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.
get_marches_publics ~202
Returns live aggregates of French public procurement contracts for websites (DECP open data, plus BOAMP price weighting) from the Les Créavores open dataset: amounts excl. VAT (n, q1, median, q3) per 'category|buyer type' (website creation/redesign, maintenance/hosting, SEO/marketing), number of bids received, yearly breakdown and publication thresholds. Optional filter by buyer type (e.g. commune, departement, region, epci_syndicat, universite, hopital_etab_sante, autres, tous). Every answer carries sources, licence, generation date and citation.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer_type | string | – | Buyer type as written in the dataset, e.g. commune, departement, region, epci_syndicat, universite, hopital_etab_sante, autres, tous |
| include_unpublishable | boolean | – | Also return cells flagged publiable=false (default false) |
No output schema declared.
No examples provided.
get_marronniers ~207
Returns live French editorial calendar dates ('marronniers') for Sept 2026 to Dec 2027 from the Les Créavores open dataset: world days, holidays, school holidays, seasons, public holidays and retail events, each with start/end date, label, type, sectors, source and a content angle. Optional filters: from/to (YYYY-MM-DD, overlap match), sector (also returns dates common to all sectors, 'tous') and limit. Every answer carries source, licence, date and citation.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Start date YYYY-MM-DD (events ending on or after it) |
| limit | integer | – | Maximum number of events returned (default 50) |
| sector | string | – | Sector as written in the dataset, e.g. sante, beaute, artisanat, restauration, immobilier, commerce, b2b |
| to | string | – | End date YYYY-MM-DD (events starting on or before it) |
No output schema declared.
No examples provided.
get_prix_site ~189
Returns live French website pricing data from the Les Créavores open dataset (prices publicly displayed by web agencies and freelancers): one cell per 'type|unit' (e.g. 'vitrine|forfait', 'maintenance|mensuel') with sample size n, number of distinct providers and p10/p25/p50/p75/p90 in euros. Optional filters by type and unit; only publishable cells are returned by default. Every answer carries source, licence, generation date and citation.
| Name | Type | Req | Description |
|---|---|---|---|
| include_unpublishable | boolean | – | Also return cells flagged publiable=false (default false) |
| type | string | – | Site/service type as written in the dataset, e.g. vitrine, e-commerce, one_page, seo, maintenance |
| unit | string | – | Pricing unit as written in the dataset, e.g. forfait (one-off) or mensuel (monthly) |
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.
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
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 audit of any URL + French open data: website prices, public tenders, editorial calendar. 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 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 11 tools: audit_aeo, check_direct_answer, extract_structured_data, check_llms_txt, check_eeat_signals, and 6 more. Their descriptions and schemas cost roughly 1,396 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 21 November 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.
What did VerifyMCP test on the Créavores AEO Audit MCP server?
VerifyMCP ran 16 checks on Créavores AEO Audit, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.