Robin Saige we check the tools AI agents call

TickDB Market Data

io.github.TickDB/tickdb-market-data

Real-time & historical market data: forex, stocks, crypto, indices, metals, K-line, quotes

— the operator's own registry description reported

Publisher io.github.TickDB · first seen 2026-08-12 · endpoint https://mcp.tickdb.ai/

allow
verdict
mid-slow-solo
cluster
ok_tools
answers
13
tools served

Dependency rating derived

allow
allow — alive & usable · retrieval-public ● · V0 take its word ◐
allow — because answers ●, 13 tools legible (band B) ●, no confirmed drift in 2 probes ●; not yet checked: truth (0 runs)

Cluster mid-slow-solo · distinctiveness 0.635 (unusual). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency782 ms
vs populationslow
protocolcurrent
authopen
Can it be used? Q4 · observed
tools13
vs populationmid
capabilities4
harnessB
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_75d58fc7bf73d180993766ae · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Q1Does it answer?alive & usable — 2 probes ●evidence ↓
Q2What is it?retrieval-public ● evidence ↓
Q3Can it be checked?V0 take its word ◐evidence ↓
Q4Did it hold?harness B · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?mid-slow-solo · 1 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)
datetypewhat changed
2026-08-12outcomefirst probe: ok_tools

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
retrieval-public9serves public factstruth-checkable against a public source — the V-ladder applies in full
action4changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions

Tools last seen observed

get_available_symbols get_capital_flow get_intraday get_kline get_kline_intervals get_kline_latest get_market_metrics get_order_book get_recent_trades get_stock_info get_ticker get_trade_days get_trading_sessions

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band B — usable, with rough edges.

legibility checktools passingok
name is clear & specific13/13
has a description13/13
description is substantive13/13
parameters are typed13/13
parameters are described1/131/13

13 of 13 tools graded · 13 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18
protocol version
session model
1.27.2
server version tickdb-market-data

Capabilities: experimental prompts resources tools

Drift observed

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:59:17Zok_tools2007822025-06-18
2026-08-12T05:34:30Zok_tools2006902025-06-18

Watch or embed this verdict

verdict badge

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.TickDB/tickdb-market-data.svg)](https://robinsaige.com/s/io.github.TickDB/tickdb-market-data)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview