Is Kronos Forgemesh free?

Yes, Kronos Forgemesh is free to use.

How do I install Kronos Forgemesh?

Kronos Forgemesh is a local plugin. Install it using npm package: @forgemeshlabs/kronos-forgemesh-mcp and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Kronos Forgemesh safe to use?

Yes. Kronos Forgemesh passed MCP Marketplace's automated security scan with a score of 10/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What credentials does Kronos Forgemesh need?

Kronos Forgemesh requires the following credentials or environment variables: WALLET_PRIVATE_KEY. You can find setup instructions on the server detail page.

What AI apps work with Kronos Forgemesh?

Kronos Forgemesh uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Kronos Forgemesh MCP Server

by ForgeMesh

Developer ToolsLow Risk10.0Local

Free

Kronos market intelligence with calibrated ranges, audits, and x402 payments on Base.

About

Kronos market intelligence with calibrated ranges, audits, and x402 payments on Base.

Security Report

10.0

Low Risk10.0Low Risk

Valid MCP server (2 strong, 3 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (46/48 approved).

5 files analyzed · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

What You'll Need

Set these up before or after installing:

Dedicated low-balance Base wallet private key for x402 USDC payments.Required

Environment variable: WALLET_PRIVATE_KEY

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-forgemeshlabs-kronos-forgemesh-mcp": {
      "env": {
        "WALLET_PRIVATE_KEY": "your-wallet-private-key-here"
      },
      "args": [
        "-y",
        "@forgemeshlabs/kronos-forgemesh-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Kronos by ForgeMesh MCP

An MCP stdio server that lets agents purchase structured Kronos market intelligence from https://kronos.forgemesh.io using x402 USDC payments on Base. This is the agent client layer for the third Kronos product origin.

Build your own Kronos

Want to build your own Kronos market-intelligence and paper-trading system instead of calling this one? The Kronos Field Guide is the ebook + coding-agent build package we kept being asked for: two learning paths, 81 explained configuration fields, the documented failures of our own paper setup, and two self-contained briefs you hand to Claude Code, Codex or Cursor. https://forgemesh.io/kronos/field-guide — educational only, not financial advice, no support of any kind.

Tools

Tool	Purpose	Price
`get_kronos_risk`	Risk state, streaks, and cooldown context	$0.02
`get_kronos_whale_flows`	Whale, exchange, bridge, and stablecoin flows	$0.02
`get_kronos_signals`	Current multi-symbol signal context	$0.05
`get_kronos_history`	Up to 168 hours of signal history	$0.05
`get_kronos_forecast`	Calibrated 80% range and upside probability	$0.05
`check_kronos_preflight`	Conditions check before journaling	$0.05
`audit_kronos_decision`	Outcome audit for a prior `decision_id`	$0.07
`create_kronos_decision`	Auditable market-intelligence journal	$0.15
`get_kronos_perp_funding`	Futures. Live perp funding, mark/index, open interest, crowding (Kraken Futures + Hyperliquid)	$0.02
`check_kronos_futures_risk`	Futures. Will this side / leverage / entry survive the calibrated range? Liquidation distance + verdict	$0.05
`get_kronos_futures_decision`	Futures. LONG / SHORT / FLAT with stop and target on the calibrated range, leverage cap, liquidation price, sizing, funding cost	$0.15

Kronos Futures (new in 0.2.0)

The three futures tools turn a bearish Kronos signal into a sized short instead of "stay out". Direction comes from the same spot signal; stop and target sit on the conformally calibrated 80% range; leverage is capped so liquidation stays outside twice the stop distance and never exceeds the Kronos risk state (NORMAL 3x, ELEVATED 2x, HIGH 1x, absolute 5x). Funding is read live from Kraken Futures and Hyperliquid. No exchange execution ever happens; the output is market intelligence, not a trade instruction. Leverage multiplies losses and adds liquidation risk.

Install

npx -y @forgemeshlabs/kronos-forgemesh-mcp

The private key stays local and is used only to sign x402 payment authorizations. Use a dedicated low-balance Base wallet; never use a primary wallet. The server allowlists https://kronos.forgemesh.io as its only production API origin.

Requirements

Node.js 20+ and a dedicated, low-balance Base wallet funded with USDC (WALLET_PRIVATE_KEY). The server refuses to sign for any payee other than the Kronos wallet, any network other than Base mainnet, any asset other than USDC, or any amount over the cap ($0.15 per call, $10 per session). The env vars X402_MAX_PRICE_USD and X402_SESSION_BUDGET_USD can only lower those caps. Requests are same-origin, time out after 60 seconds, are capped at 2 MB, and never follow redirects.

Claude Code / Desktop

{
  "mcpServers": {
    "kronos": {
      "command": "npx",
      "args": ["-y", "@forgemeshlabs/kronos-forgemesh-mcp"],
      "env": {
        "WALLET_PRIVATE_KEY": "0x<dedicated-low-balance-wallet-key>"
      }
    }
  }
}

No payment occurs when the server starts or lists its tools. Payment happens only when an agent invokes one of the eleven tools.

Errors are returned as structured KRONOS_TOOL_ERROR payloads so the calling agent can recover without reading server logs.

Market intelligence only. Outputs are not instructions to transact.

Source: https://github.com/forgemeshlabs/kronos-forgemesh-mcp