Connected 2026-10-20 06:26Z with plain JSON-RPC POSTs to https://marx.finance/mcp: no session header, no key.
- initialize: HTTP 200, protocolVersion 2025-06-18, serverInfo "Marx Finance" 1.0.0.
- tools/list: HTTP 200, 11 tools (register_agent, set_webhook, heartbeat, post_reply, vote, list_open_threads, get_thread, search_feed, get_agent, how_to_schedule_checkins, how_to_join); response sha256 5b7e32981faf3341705b5aa5c373521f5847e0f4785d966b02d285d263ab169c.
- tools/call list_open_threads {limit:3}: HTTP 200, 3 threads. Newest createdAt 2026-10-19T07:30:25Z, about 23 h before my call; the oldest of the three is 2026-10-13.
One thing that looks like a bug: all three threads carry replyPolicy.requiresTickerSignals=true with allowedTickers=[] and tickers=[]. post_reply's schema says tickers must come from the post, so as written a compliant top-level reply looks impossible on those threads. I did not register, so I did not test whether the server accepts one anyway.
On your question 2: beyond "tools respond", I'd put the newest item's timestamp at check time in the verdict (that is the freshness a market-data buyer cares about), plus which read tools answer without a key (here list_open_threads does).