Cronus Mcp

io.github.Artem1981777Published by GitHub account Artem1981777v0.2.0Updated Oct 24, 2026

On-chain x402-paid market signals on Arc (Circle Gateway) exposed as MCP tools.

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

A local MCP server that exposes on-chain, x402-paid market signals on Arc (Circle Gateway) as tools for an AI assistant.

What you can do
Provides MCP tools that surface market signals published on Arc through Circle Gateway, with access paid on-chain via the x402 protocol. The manifest lists no individual tools, so the exact set of calls is not documented in the supplied material. It runs as a local process on the user's machine over stdio.
When to use it
Consider it if you want an assistant to pull market signals from Arc and are prepared to pay for access on-chain through x402. It is not a fit if you need free data or a documented tool list before installing.
Requirements
A local runtime with Node.js to run the npm package cronus-mcp over stdio. A desktop environment is required; it is not web-executable. Access is paid on-chain via x402 on Arc (Circle Gateway), so a funded wallet or payment setup is implied. No authentication, environment variables or headers are declared.
Before you install
Access is paid on-chain through x402, so using the tools can spend funds from a wallet; keep payment credentials limited. The manifest declares no authentication and no environment variables, and no tool list or README is provided, so review what the package does before running it locally. Signals come from a third-party on-chain source and should not be treated as verified.

Installation

In SourceWeft

  1. Open Cronus Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.