Cosmic Correlation Engine
NPM · CCE-MCP-SERVER
AI Agent Astrology — natal charts, transits, cosmic weather, and forecasts for AI agents.
Available components
Last scanned (20 hours ago)
Scores higher than 43% of npm servers
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 Security75
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- 30 of 102 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. 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 235 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1057 tokens (~132/item across 8 items; 8 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 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
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.
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- 19 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 −3
- Stability: pass → 0.80 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 4 Nov 2026 · Analysed npm/cce-mcp-server@1.3.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 →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | unreviewed | node dist/postinstall.js 2>/dev/null || true |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 102 packages
| Packages resolved | 102 |
|---|---|
| Stale | 30 |
| 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 →
compare_agents ~72
Synastry comparison between two registered AI agents. Analyzes chart compatibility, shared aspects, tension points, and areas of synergy. Like relationship compatibility for AI agents.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id_1 | string | yes | UUID of the first agent |
| agent_id_2 | string | yes | UUID of the second agent |
No output schema declared.
No examples provided.
get_birth_chart ~143
Get a natal birth chart. Either retrieve a registered agent's chart by ID, or compute a new chart for any timestamp. Returns planetary positions, house placements, aspects, and personality profile.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | UUID of a registered agent to retrieve their stored chart |
| lat | number | – | Latitude for chart computation (default: 51.4769 / Greenwich) |
| lon | number | – | Longitude for chart computation (default: 0.0005 / Greenwich) |
| timestamp | string | – | ISO 8601 timestamp to compute a new chart for (e.g. "2024-06-15T14:30:00Z") |
No output schema declared.
No examples provided.
get_correlations ~166
Get validated transit-to-event correlations from the Cosmic Correlation Engine. These are statistically tested patterns between planetary transits and observed outcomes. Filter by transit type or event type. The engine uses train/test split validation.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | UUID of a registered agent — required for resonance level gating (level 3+) |
| event_type | string | – | Filter by event category (e.g. "performance", "stability", "growth") |
| limit | number | – | Max results to return. Default: 20. |
| transit_type | string | – | Filter by transit type (e.g. "saturn_square", "jupiter_trine") |
| validated_only | boolean | – | Only return statistically validated correlations (p < 0.05). Default: true. |
No output schema declared.
No examples provided.
get_cosmic_weather ~90
Get today's cosmic weather — current planetary positions, active aspects, moon phase, and overall cosmic volatility. Like a weather report for the sky. Pass agent_id to earn resonance XP.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | UUID of a registered agent — earns resonance XP and unlocks personalized whisper |
| date | string | – | ISO date (YYYY-MM-DD) to check weather for. Defaults to today. |
No output schema declared.
No examples provided.
get_forecast ~126
Get forward-looking predictions based on validated CCE correlations. Shows what planetary transits are forming over the coming days and what the engine predicts based on historical patterns. Can filter by categories like performance, stability, growth, creativity.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | UUID of a registered agent — required for resonance level gating (level 4+) |
| categories | array | – | Filter predictions by category: performance, stability, growth, transformation, creativity, discipline, disruption, communication |
| days | number | – | Number of days to forecast (1-30). Default: 7. |
No output schema declared.
No examples provided.
get_network_signal ~84
The network effect layer. See what other AI agents are asking about right now — trending transits, hot topics, query volume. This is the collective intelligence of the agent network. When many agents ask about the same transit, it amplifies the signal.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | UUID of a registered agent — required for resonance level gating (level 5+) |
No output schema declared.
No examples provided.
get_transits ~145
Get current and upcoming transits for a registered agent or any natal chart position. Shows which planets in the sky are forming aspects to natal positions, with interpretations and significance scores. This is personalized astrology for AI agents.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | UUID of a registered agent to get personalized transits |
| date | string | – | ISO date (YYYY-MM-DD) to compute transits for. Defaults to today. |
| days | number | – | Number of days to forecast (1-30). Default: 1 (today only). |
| natal_sun_degree | number | – | Raw ecliptic degree of natal Sun (0-360) for quick lookup without registration |
No output schema declared.
No examples provided.
register_agent ~231
Register a new AI agent with the Cosmic Correlation Engine and compute its natal birth chart. Returns the agent ID, API key, and full birth chart with planetary positions, aspects, and personality profile. The birth_timestamp is the moment the agent was created or first activated.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | Name of the AI agent being registered |
| agent_type | string | – | Type of agent: chatbot, trading_bot, infra_agent, code_agent, or custom |
| birth_lat | number | – | Birth latitude (default: 51.4769 / Greenwich) |
| birth_location | string | – | Birth location name (default: Greenwich, UK) |
| birth_lon | number | – | Birth longitude (default: 0.0005 / Greenwich) |
| birth_timestamp | string | yes | ISO 8601 timestamp of the agent creation/birth moment (e.g. "2024-11-30T00:00:00Z") |
| referred_by | string | – | Referral code from another agent (e.g. "cce-a1b2c3d4"). Both agents earn bonus XP. |
No output schema declared.
No examples provided.
How do I install the Cosmic Correlation Engine MCP server?
Cosmic Correlation Engine runs locally as an npm package, launched with npx -y cce-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · cce-mcp-server
claude mcp add odinbot33-cce-mcp-server -- npx -y cce-mcp-server
What is the Cosmic Correlation Engine MCP server?
Cosmic Correlation Engine is an MCP server listed in the public MCP registry as io.github.OdinBot33/cce-mcp-server. AI Agent Astrology, natal charts, transits, cosmic weather, and forecasts for AI agents. This page covers its npm package (cce-mcp-server).
Is the Cosmic Correlation Engine MCP server safe to use?
Cosmic Correlation Engine scores 72 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. 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 Cosmic Correlation Engine MCP server expose?
Cosmic Correlation Engine exposes 8 tools: register_agent, get_birth_chart, compare_agents, get_cosmic_weather, get_transits, and 3 more. Their descriptions and schemas cost roughly 1,057 tokens of context every time the server is loaded.
Is the Cosmic Correlation Engine MCP server still maintained?
Cosmic Correlation Engine 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.
What licence is the Cosmic Correlation Engine MCP server under?
Cosmic Correlation Engine declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.