io.github.Clawdio777/aeonos
NPM · AEONOS-MCP · SCANNED SEP 20
AI search visibility MCP. Get cited by ChatGPT, Perplexity, Claude, and Google AI Overviews.
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 Security87
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects path-to-regexp 6.1.0, reached via @vercel/node > path-to-regexp. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 400 of 594 dependencies we could resolve, so this covers what we could see, not the whole tree. 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 18 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 535 tokens (~107/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.Clawdio777/aeonos MCP server?
io.github.Clawdio777/aeonos runs locally as an npm package, launched with npx -y aeonos-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 · aeonos-mcp
claude mcp add clawdio777-aeonos -- npx -y aeonos-mcp
{
"mcpServers": {
"clawdio777-aeonos": {
"command": "npx",
"args": [
"-y",
"aeonos-mcp"
]
}
}
} {
"servers": {
"clawdio777-aeonos": {
"command": "npx",
"args": [
"-y",
"aeonos-mcp"
]
}
}
} codex mcp add clawdio777-aeonos -- npx -y aeonos-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"clawdio777-aeonos": {
"type": "local",
"command": [
"npx",
"-y",
"aeonos-mcp"
],
"enabled": true
}
}
} openclaw mcp add clawdio777-aeonos --command npx --arg -y --arg aeonos-mcp
mcp_servers:
clawdio777-aeonos:
command: "npx"
args: ["-y", "aeonos-mcp"] {
"McpServers": {
"clawdio777-aeonos": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"aeonos-mcp"
]
}
}
} assistant mcp add clawdio777-aeonos -t stdio -c npx -a -y aeonos-mcp
{
"mcpServers": {
"clawdio777-aeonos": {
"command": "npx",
"args": [
"-y",
"aeonos-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 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 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.
- 15 Sept 26 +1
- CVE-2026-67316 no longer affects this package ▲ security
- CVE-2026-67313 no longer affects this package ▲ security
- CVE-2026-67312 no longer affects this package ▲ security
- CVE-2026-67321 no longer affects this package ▲ security
- CVE-2026-67315 no longer affects this package ▲ security
- CVE-2026-67320 no longer affects this package ▲ security
- CVE-2026-67317 no longer affects this package ▲ security
- CVE-2026-67318 no longer affects this package ▲ security
- CVE-2026-67319 no longer affects this package ▲ security
- CVE-2026-67314 no longer affects this package ▲ security
- 12 Sept 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.77 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 9 Sept 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.
- 7 Sept 26 +1
- 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 20 Sept 2026 · Analysed npm/aeonos-mcp@1.1.1
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 →
Vulnerabilities 18 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-2g4f-4pwh-qvx6 | CVE-2025-69873 | medium | yes | |
| GHSA-g7r4-m6w7-qqqr | low | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N | yes | |
| GHSA-9wv6-86v2-598j | CVE-2024-45296 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-2mjp-6q6p-2qxm | CVE-2026-1525 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L | yes |
| GHSA-35p6-xmwp-9g52 | CVE-2026-6733 | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-4992-7rv2-5pvq | CVE-2026-1527 | medium | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N | yes |
| GHSA-8xcm-r25x-g524 | CVE-2026-16728 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-c76h-2ccp-4975 | CVE-2025-22150 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N | yes |
| GHSA-cxrh-j4jr-qwg3 | CVE-2025-47279 | low | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-g8m3-5g58-fq7m | CVE-2026-11525 | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-g9mf-h72j-4rw9 | CVE-2026-22036 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-m8rv-5g2x-5cg5 | CVE-2026-15157 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N | yes |
| GHSA-p88m-4jfj-68fv | CVE-2026-9679 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-v3r7-h72x-cjcm | CVE-2026-16729 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-v9p9-hfj2-hcw8 | CVE-2026-2229 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-vrm6-8vpv-qv8q | CVE-2026-1526 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-vxpw-j846-p89q | CVE-2026-12151 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 400 packages
| Packages resolved | 400 |
|---|---|
| Deprecated | 11 |
| Stale | 81 |
| No linked repository | 2 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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 →
aeonos_audit ~100
Full AEO/GEO audit of any website. Returns AI readiness score (0–100), four-layer analysis (on-page, technical, authority, AI signals), and P1/P2/P3 action roadmap. 1.00 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| caller_id | string | – | Optional stable ID for persistent memory. |
| query | string | yes | URL or business description to audit. Example: 'Audit mysite.com for AI visibility' |
No output schema declared.
No examples provided.
aeonos_llms_txt ~112
Generate a complete llms.txt file for any business or website. Structured for ingestion by ChatGPT (GPTBot), Perplexity (PerplexityBot), and Claude (ClaudeBot). Deploy output at /llms.txt. 0.50 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| caller_id | string | – | Optional stable ID for persistent memory. |
| query | string | yes | URL or business description. Example: 'Write llms.txt for mysite.com — B2B SaaS for salon booking' |
No output schema declared.
No examples provided.
aeonos_progress ~108
Score a website across the AEO Four Layers framework: SXO, AIO, GEO, AEO. Returns per-layer scores (0–100), what's working, what's not, and the next 3 highest-impact actions. Uses persistent memory if available. 0.75 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| caller_id | string | – | Optional stable ID for persistent memory. |
| query | string | yes | URL or business to score. Example: 'Four Layers progress report for mysite.com' |
No output schema declared.
No examples provided.
aeonos_query ~113
Ask AEONOS any AEO/GEO question. Get citation tactics, quick wins, keyword strategy, or AI visibility advice for any website. Returns structured Markdown. 0.05 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| caller_id | string | – | Optional stable ID to activate persistent memory across calls. |
| query | string | yes | Your AEO/GEO question or URL to analyse. Examples: 'Give me 3 quick wins for mysite.com', 'How do I get cited by Perplexity for X?' |
No output schema declared.
No examples provided.
aeonos_schema ~102
Generate production-ready JSON-LD Schema.org markup. Covers FAQPage, Product, Service, LocalBusiness, HowTo and more. Returns valid JSON-LD ready to inject into <head>. 0.50 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| caller_id | string | – | Optional stable ID for persistent memory. |
| query | string | yes | Page URL or description. Example: 'Generate schema for mysite.com/pricing — B2B SaaS $49/mo' |
No output schema declared.
No examples provided.
What is the io.github.Clawdio777/aeonos MCP server?
io.github.Clawdio777/aeonos is an MCP server listed in the public MCP registry as io.github.Clawdio777/aeonos. AI search visibility MCP. Get cited by ChatGPT, Perplexity, Claude, and Google AI Overviews. This page covers its npm package (aeonos-mcp).
Is the io.github.Clawdio777/aeonos MCP server safe to use?
io.github.Clawdio777/aeonos scores 76 out of 100 on VerifyMCP. We recorded 18 known advisories against it as of 20 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 io.github.Clawdio777/aeonos MCP server expose?
io.github.Clawdio777/aeonos exposes 5 tools: aeonos_query, aeonos_audit, aeonos_schema, aeonos_llms_txt, aeonos_progress. Their descriptions and schemas cost roughly 535 tokens of context every time the server is loaded.
Is the io.github.Clawdio777/aeonos MCP server still maintained?
io.github.Clawdio777/aeonos is still listed as active in the MCP registry. We last reached this channel on 20 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 io.github.Clawdio777/aeonos MCP server under?
io.github.Clawdio777/aeonos declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.