Release v1.4.1 — prompts, two stubs turned real, CI · dziuba0x/flario

Flario is now in the official MCP Registry as io.github.dziuba0x/flario.

Five prompts, no Flare knowledge required

Tools answer questions. Prompts tell you what to ask. These show up in your client's prompt list and drive real calls against the live network:

Show me what Flare can do — a guided tour: a price, the same price carrying a proof you verify locally, FAssets state
Verify a price without trusting anyone — walks through exactly what earned the verified: true: which leaf, which fold, which contract the root came from
Turn a web API into a provable fact — Web2Json end to end, including the trap that a valid proof only proves the data came from the URL inside it
Check FAssets system health — live agent collateral against live prices
Why Flare, for someone building agents — the case for and against, including where the ecosystem is weak

get_ftso_providers used to fail on install unless you pointed it at an indexer that does not exist publicly. It now reads the VoterRegistry directly and ranks providers by share of normalised vote weight. 100 providers on mainnet, 65 on Songbird, no external service.
get_smart_account_info guessed at a `getFlareAddress` function that does not exist. It now uses `getPersonalAccount` and `isSmartAccount` from the published interface, resolves both directions, and distinguishes a reserved address from a deployed one.

CI on Node 20, 22 and 24, plus a cold-start job that spawns the built server over stdio with no env vars — the exact path a new user's client takes on first run
`server.json` and `mcpName` for registry ownership validation
`live-check` reports stale verifier fixtures as SKIP instead of failing the run

21 tools, 5 prompts, 2 resources, 96 tests.