kronos-forgemesh-mcp
Official# Kronos by ForgeMesh MCP
[](https://m8ven.ai/mcp/forgemeshlabs-kronos-forgemesh-mcp-1dod5h)
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 |
## Install
```bash
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.
## Claude Code / Desktop
```json
{
"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 eight tools.
Unpaid challenge requests time out after 30 seconds; paid retries time out
after 60 seconds. 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
TDQS
Scored across 8 tools
Each tool targets a distinct aspect of the Kronos market-intelligence domain: signals, risk, history, forecast, preflight checks, decision journaling, auditing, and whale flows. The only minor overlap is between risk and preflight (both mention cooldowns), but their purposes are clearly separated: one describes market risk state, the other is a pre-decision suitability check.
All tool names follow a consistent verb_kronos_noun pattern in snake_case (get_kronos_*, check_kronos_*, create_kronos_*, audit_kronos_*). The verb prefix clearly indicates the action, and the resource name is always kronos plus a specific suffix, making the set highly predictable.
With 8 tools, the server is well-scoped for a market-intelligence and decision-journaling service. Each tool covers a distinct need without redundancy or bloat, and the count comfortably fits within the ideal range.
The server provides a solid coverage of the Kronos workflow: retrieving signals/risk/forecast, checking preconditions, creating auditable decisions, and auditing past decisions. A minor gap is the lack of a tool to fetch or list decision entries directly (only audit by decision_id), but this is workable and does not break the core workflow.