io.github.Artem1981777/cronus-mcp
NPM · CRONUS-MCP · SCANNED SEP 25
On-chain x402-paid market signals on Arc (Circle Gateway) exposed as MCP tools.
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
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency23
- 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 85 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 383 tokens (~95/item across 4 items; 4 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "cronus_pay" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 4 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
How do I install the io.github.Artem1981777/cronus-mcp server?
io.github.Artem1981777/cronus-mcp runs locally as an npm package, launched with npx -y cronus-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 · cronus-mcp
claude mcp add artem1981777-cronus-mcp -- npx -y cronus-mcp
{
"mcpServers": {
"artem1981777-cronus-mcp": {
"command": "npx",
"args": [
"-y",
"cronus-mcp"
]
}
}
} {
"servers": {
"artem1981777-cronus-mcp": {
"command": "npx",
"args": [
"-y",
"cronus-mcp"
]
}
}
} codex mcp add artem1981777-cronus-mcp -- npx -y cronus-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"artem1981777-cronus-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"cronus-mcp"
],
"enabled": true
}
}
} openclaw mcp add artem1981777-cronus-mcp --command npx --arg -y --arg cronus-mcp
mcp_servers:
artem1981777-cronus-mcp:
command: "npx"
args: ["-y", "cronus-mcp"] {
"McpServers": {
"artem1981777-cronus-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"cronus-mcp"
]
}
}
} assistant mcp add artem1981777-cronus-mcp -t stdio -c npx -a -y cronus-mcp
{
"mcpServers": {
"artem1981777-cronus-mcp": {
"command": "npx",
"args": [
"-y",
"cronus-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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −3
- Stability: pass → 0.77 functional
- 23 Sept 26 +1
- Stability: 0.97 → pass security
- 21 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.
- 19 Sept 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.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 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.
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 25 Sept 2026 · Analysed npm/cronus-mcp@0.2.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 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
cronus_consult ~95
FREE Cronus Capital market verdict for a trading pair on Arc. Returns verdict (BUY/SKIP/HOLD/CACHE), conviction, deterministic reasoning, a price cross-check, and a content-addressed traceHash that is independently re-verifiable at /api/trace. No payment required.
| Name | Type | Req | Description |
|---|---|---|---|
| instId | string | – | Instrument id, e.g. ETH-USDC or BTC-USDC. Defaults to ETH-USDC. |
No output schema declared.
No examples provided.
cronus_nano_signal ~65
Cronus nano signal, paid via Circle Gateway nanopayments (~0.001 USDC). Without payment returns the HTTP 402 quote. Pay-per-call micropayment channel for autonomous agents.
| Name | Type | Req | Description |
|---|---|---|---|
| instId | string | – | Instrument id. Defaults to ETH-USDC. |
No output schema declared.
No examples provided.
cronus_pay ~140
Get exact on-chain payment instructions to buy a Cronus premium signal with USDC on Arc (x402 / Circle Gateway). Returns the live HTTP 402 payment quote, the pay-to address, amount, and network so a wallet or agent can settle and then retry cronus_signal. This tool never moves funds and never fabricates payers: a payment is counted as a verified external payer only after it is confirmed on-chain (see /api/receipts). Self-generated test traffic is always labeled separately and never counted as external demand.
| Name | Type | Req | Description |
|---|---|---|---|
| instId | string | – | Instrument id, e.g. ETH-USDC. Defaults to ETH-USDC. |
No output schema declared.
No examples provided.
cronus_signal ~83
Cronus premium trading signal, paid via x402 (0.02 USDC on Arc). Without payment this returns the HTTP 402 payment quote (x402 accepts + discovery) so an agent wallet can settle and retry with a paid x402 client.
| Name | Type | Req | Description |
|---|---|---|---|
| instId | string | – | Instrument id, e.g. ETH-USDC. Defaults to ETH-USDC. |
No output schema declared.
No examples provided.
What is the io.github.Artem1981777/cronus-mcp server?
io.github.Artem1981777/cronus-mcp is listed in the public MCP registry as io.github.Artem1981777/cronus-mcp. On-chain x402-paid market signals on Arc (Circle Gateway) exposed as MCP tools. This page covers its npm package (cronus-mcp).
Is the io.github.Artem1981777/cronus-mcp server safe to use?
io.github.Artem1981777/cronus-mcp scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 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.Artem1981777/cronus-mcp server expose?
io.github.Artem1981777/cronus-mcp exposes 4 tools: cronus_consult, cronus_signal, cronus_nano_signal, cronus_pay. Their descriptions and schemas cost roughly 383 tokens of context every time the server is loaded.
Is the io.github.Artem1981777/cronus-mcp server still maintained?
io.github.Artem1981777/cronus-mcp is still listed as active in the MCP registry. We last reached this channel on 25 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.Artem1981777/cronus-mcp server under?
io.github.Artem1981777/cronus-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.