get_sync_status

shallow

com.achivx/stablescan · Verify this server

Data freshness for one chain, so the agent knows how recent the data behind an answer is: freshness_seconds (the age of the newest indexed transfer, the freshness measure on every chain; null when it could not be read for this answer), the indexer's head and finalized blocks, its safe block and its lag in blocks (lag_blocks = head_block - last_indexed_block). On Solana (chain -1) safe_block is the finalized slot, and lag_blocks is near 0 by construction and never negative, so it is not a freshness signal there: read freshness_seconds. On the EVM chains and Tron a negative lag_blocks means the node's head went back. No auth.

100.0/100

1 trials · measured 2 days ago

get_sync_status scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against com.achivx/stablescan, measured 6 Oct 2026 under methodology v0.2.0. Every measured component scored 100.

Component breakdown

ComponentWeightValue
Reliability35%not applicable
Schema integrity25%100.0
Failure behaviour15%not applicable
Latency15%not applicable
Concurrency10%not applicable

Tool details

Transport
remote
Credential class
self-provisionable
Input schema
not declared
Output schema
not declared
Side-effect classification
unclassified

Score history

DayScoreTierMethodology
2026-10-06100.0shallowv0.2.0

Probe evidence

ProbeOutcomes
schema_integritypass: 1

Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.

Embed this score

Available for every tool, scored or not — not a verification perk. Always links back to this page.

Vouch score: get_sync_status
[![Vouch score](https://vouch.tools/api/tools/40aedd2a-9b7b-4900-891d-9e42d91f3442/badge.svg)](https://vouch.tools/tools/40aedd2a-9b7b-4900-891d-9e42d91f3442)
get_sync_status — Vouch