Skip to main content
Glama
forgemeshlabs

kronos-forgemesh-mcp

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WALLET_PRIVATE_KEYYesThe private key of a dedicated low-balance Base wallet used to sign x402 payment authorizations. Never use a primary wallet.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_kronos_signalsA

Get current Kronos signal context and ranked symbols for BTC, ETH, SOL, XRP, and ADA. Costs $0.05 USDC.

get_kronos_riskA

Get current Kronos market-risk state, signal streaks, and cooldown context. Costs $0.02 USDC.

get_kronos_historyA

Get up to 168 hours of timestamped Kronos signal history for analysis and audit support. Costs $0.05 USDC.

get_kronos_forecastA

Get a conformally calibrated 80% price range, current price, and upside probability for a supported symbol. Costs $0.05 USDC.

check_kronos_preflightA

Check market state, cooldowns, freshness, and warnings before creating a Kronos decision journal. Costs $0.05 USDC.

create_kronos_decisionA

Create an auditable Kronos market-intelligence journal entry with directional bias, calibrated confidence, and decision_id. Costs $0.15 USDC.

audit_kronos_decisionA

Audit a prior Kronos decision_id against later prices and return its outcome verdict. Costs $0.07 USDC.

get_kronos_whale_flowsA

Get whale, exchange, bridge, and stablecoin-flow context for Ethereum, Base, or Arbitrum. Costs $0.02 USDC.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 8 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues