# Flario (npm · flario)

Flare for agents: FTSO prices with locally verified Merkle proofs, FDC, FAssets, x402 pay.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- npm · `flario`: 80/100 (this document), [markdown](https://verifymcp.io/servers/dziuba0x-flario/flario.md), [page](https://verifymcp.io/servers/dziuba0x-flario/flario)

## Channel facts

- Registry: `npm`
- Package: `flario`
- Version: `1.6.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 35 of 120 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 23 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 2535 tokens (~97/item across 26 items; 24 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 74/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 21% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Flario MCP server?

Flario runs locally as an npm package, launched with npx -y flario. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add dziuba0x-flario -- npx -y flario
```

### Cursor

```json
{
  "mcpServers": {
    "dziuba0x-flario": {
      "command": "npx",
      "args": [
        "-y",
        "flario"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dziuba0x-flario": {
      "command": "npx",
      "args": [
        "-y",
        "flario"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dziuba0x-flario -- npx -y flario
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dziuba0x-flario": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "flario"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dziuba0x-flario --command npx --arg -y --arg flario
```

### Hermes

```yaml
mcp_servers:
  dziuba0x-flario:
    command: "npx"
    args: ["-y", "flario"]
```

### Netclaw

```json
{
  "McpServers": {
    "dziuba0x-flario": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "flario"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dziuba0x-flario -t stdio -c npx -a -y flario
```

### Other

```json
{
  "mcpServers": {
    "dziuba0x-flario": {
      "command": "npx",
      "args": [
        "-y",
        "flario"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-23 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (24)

### `get_flr_balance` (~56 tokens)

Get native FLR balance and wrapped WFLR (WNat) balance for an EVM address on Flare mainnet or Coston2 testnet.

Input parameters:

- `address` (string, required)
- `network` (string, required)

### `get_flr_stake_info` (~69 tokens)

One-call Flare portfolio for an address: native FLR + wrapped WFLR, FTSO vote power and delegation, claimable protocol rewards (by source), and FlareDrops. All four networks.

Input parameters:

- `address` (string, required)
- `network` (string, required)

### `get_ftso_feed` (~61 tokens)

Get the latest FTSO price feed (value, decimals, timestamp) for a feed by name (e.g. "FLR/USD") or raw bytes21 feed id.

Input parameters:

- `feed_id` (string, required)
- `network` (string, required)

### `get_ftso_feeds_all` (~35 tokens)

Get the latest FTSO price for all known feeds on the given network.

Input parameters:

- `network` (string, required)

### `get_ftso_providers` (~72 tokens)

Get the list of active FTSO data providers (name, address, vote power, fee, reward rate) for the given network.

Input parameters:

- `limit` (integer)
- `network` (string, required)
- `reward_epoch_id` (integer): Reward epoch to read. Defaults to the current one.

### `get_ftso_anchor_feed` (~97 tokens)

Get a proof-carrying FTSO Scaling anchor feed: the price plus a Merkle proof verified LOCALLY against the on-chain Relay root (FTSO Scaling protocol 100). Trust-minimized — usable by an agent or a smart contract without trusting the DA API. Defaults to the latest finalized round.

Input parameters:

- `feed_id` (string, required)
- `network` (string, required)
- `voting_round_id` (integer)

### `get_ftso_history` (~89 tokens)

Get recent FTSO Scaling anchor-feed history for a feed (by name or bytes21 id) from the public Flare Data Availability layer — no external indexer needed. Each point is optionally Merkle-verified against the on-chain Relay root.

Input parameters:

- `feed_id` (string, required)
- `network` (string, required)
- `rounds` (integer)
- `verify` (boolean)

### `get_fassets_status` (~64 tokens)

Get FAssets status (total minted, active agent count) for FXRP, FBTC or FDOGE on the given network, via the on-chain AssetManager with a flaremetrics.io fallback.

Input parameters:

- `asset` (string, required)
- `network` (string, required)

### `get_fdc_proof_status` (~56 tokens)

Get the FDC (protocol id 200) Merkle root and finalization status for a voting round from the Flare Relay contract.

Input parameters:

- `network` (string, required)
- `voting_round_id` (integer, required)

### `get_smart_account_info` (~136 tokens)

Resolve between XRPL accounts and Flare Smart Accounts via the on-chain MasterAccountController. Forward: give an XRPL account (r...) to get its deterministic Flare address and whether the account is actually deployed yet. Reverse: give a Flare address (0x...) to find out whether it is a Smart Account and which XRPL account owns it.

Input parameters:

- `flare_address` (string): Flare address (0x...). Resolves backward to its XRPL owner.
- `network` (string, required)
- `xrpl_address` (string): XRPL account (r...). Resolves forward to its Flare address.

### `fdc_request_attestation` (~115 tokens)

Submit an FDC attestation request (Payment, AddressValidity or EVMTransaction). Prepares the request via a Flare-hosted verifier, queries the request fee, and — if FLARE_PRIVATE_KEY is set — submits it to FdcHub, returning the tx hash and voting round id. Without a key it returns the prepared request for external submission.

Input parameters:

- `attestation_type` (string, required)
- `network` (string, required)
- `request_body` (object, required)
- `source_chain` (string, required)

### `fdc_get_attestation_proof` (~76 tokens)

Retrieve an FDC attestation proof from the Data Availability layer for a finalized voting round and verify the Merkle proof locally against the on-chain Relay root (no trust in the DA response).

Input parameters:

- `abi_encoded_request` (string, required)
- `network` (string, required)
- `voting_round_id` (integer, required)

### `fassets_agent_status` (~71 tokens)

List FAssets agents (FXRP first) with collateral ratios, minting capacity (free lots), minted/reserved amounts and liquidation status, sorted by vault collateral ratio (riskiest first).

Input parameters:

- `asset` (string, required)
- `max_agents` (integer)
- `network` (string, required)

### `fassets_system_state` (~65 tokens)

Global FAssets system state for an asset: total minted, agent count, lot size, minting cap/pause, aggregated vault+pool collateral, and the redemption queue (tickets, value, lots).

Input parameters:

- `asset` (string, required)
- `network` (string, required)

### `fassets_agent_details` (~74 tokens)

Human-facing details of a FAssets agent (name, description, icon/logo URL, terms-of-use URL, whitelist status) from the AgentOwnerRegistry. Accepts an agent vault address or an owner management address.

Input parameters:

- `agent` (string, required)
- `asset` (string)
- `network` (string, required)

### `fassets_liquidation_scanner` (~123 tokens)

PREMIUM (x402): FAssets agents ranked by liquidation risk, joined with live FTSOv2 prices — per agent: CR headroom, the underlying price at which liquidation starts, and the % price move away from it. Free when the operator has not enabled x402.

Input parameters:

- `asset` (string, required)
- `max_agents` (integer)
- `network` (string, required)
- `x402_payment` (string): x402 payment: base64-encoded JSON EIP-3009 authorization payload. Omit to receive payment requirements.

### `fdc_bulk_proof_bundle` (~99 tokens)

PREMIUM (x402): batch retrieval of up to 20 FDC attestation proofs with local Merkle verification of each against the on-chain Relay root. Free when the operator has not enabled x402.

Input parameters:

- `network` (string, required)
- `requests` (array, required)
- `x402_payment` (string): x402 payment: base64-encoded JSON EIP-3009 authorization payload. Omit to receive payment requirements.

### `songbird_fcc_registry` (~68 tokens)

Scan the live FlareContractRegistry (Songbird by default) for Flare Confidential Compute contracts (PMW, TEE, compute extensions). Reports FCC deployment status post-STP.13 and lists FDC/Relay contracts plus the full registry.

Input parameters:

- `network` (string)

### `fdc_web2json_request` (~205 tokens)

Turn any public web API into a fact a smart contract can verify. Prepares an FDC Web2Json attestation request (URL + jq filter + ABI signature) through a Flare-hosted verifier and quotes the request fee. Submits on-chain only if FLARE_PRIVATE_KEY is set and submission is permitted; otherwise returns the prepared request for your own signer.

Input parameters:

- `abi_signature` (string, required): JSON ABI tuple describing the decoded struct, e.g. {"components":[{"internalType":"uint256","name":"price","type":"uint256"}],"name":"dto","type":"tuple"}
- `body` (string)
- `headers` (string)
- `http_method` (string)
- `network` (string, required)
- `post_process_jq` (string, required): jq filter applied to the JSON response, e.g. "{price: .price|tonumber}"
- `query_params` (string)
- `url` (string, required)

### `fdc_verify_web2json` (~155 tokens)

Verify a Web2Json attestation AND bind it to the source you expected. Checks the Merkle proof locally against the on-chain Relay root, confirms the attested URL matches your expected host / path / protocol / method, then decodes the payload with the request's ABI signature. Without expect_source the proof is verified but NOT bound, which an attacker can exploit with a valid proof from their own endpoint.

Input parameters:

- `abi_encoded_request` (string, required)
- `expect_source` (object): The source you expected. Without it the proof is verified but NOT bound, which leaves you open to a valid proof from an attacker's endpoint.
- `network` (string, required)
- `voting_round_id` (integer, required)

### `fdc_verify_settlement` (~186 tokens)

Prove an x402 settlement via Flare's enshrined FDC (trust-minimized, not the facilitator's word). Given a settlement tx hash it prepares an EVMTransaction attestation request (phase 1, free, no chain write); given a finalized voting_round_id + abi_encoded_request it locally Merkle-verifies the attestation AND binds it to the payment — confirming the attested tx contains an ERC-20 Transfer of >= amount of asset to payee. Never submits on-chain itself.

Input parameters:

- `abi_encoded_request` (string)
- `amount` (string, required)
- `asset` (string, required)
- `network` (string, required)
- `payee` (string, required)
- `payer` (string)
- `required_confirmations` (integer)
- `settlement_tx_hash` (string, required)
- `voting_round_id` (integer)

### `fcc_deployment_status` (~194 tokens)

Watch Flare 2.0 confidential compute roll out, network by network, while it is still happening. Reads the ContractRegistry for a confidential-compute deployment; if it finds an ERC-2535 diamond it enumerates every facet and function selector, maps them to capabilities (Protocol Managed Wallets, enclave VRF, machine remote-attestation, TEE governance, FDC V2), reads what it is wired to, and reports whether the system has live governance state or is an empty shell. Flare has not published an ABI for these contracts, so names come from signature matching while selectors, facets, addresses and wiring are read exactly from the chain.

Input parameters:

- `include_deployment_block` (boolean): Binary-search the first block where the contract had code. Accurate, but ~30 extra RPC calls per contract.
- `network` (string): A single network, or all four to see the rollout front.

### `evidence_bundle` (~195 tokens)

Package several proof-carrying facts into one portable bundle that someone else can verify without trusting you. Takes FTSO Scaling anchor feeds and finalized FDC attestations (Web2Json included), folds each Merkle proof against the on-chain Relay root BEFORE including it, and refuses any fact that fails. Use when an agent needs to hand a downstream consumer, an auditor, or another agent the evidence its decision rested on.

Input parameters:

- `attestations` (array): Finalized FDC attestations to include, by round and request bytes.
- `claim` (string): Plain-language statement of what these facts are being used to support.
- `ftso_feeds` (array): Feed names or bytes21 ids to anchor, e.g. ["FLR/USD", "BTC/USD"].
- `network` (string, required)
- `voting_round_id` (integer): Round for the FTSO feeds. Defaults to the latest finalized round.

### `evidence_verify` (~129 tokens)

Verify an evidence bundle from scratch. Rebuilds every leaf from its own body, folds it through its proof, and compares against Relay.merkleRoots(protocol, round) read on-chain right now. Re-binds Web2Json facts to the source recorded in the bundle. Trusts nothing in the bundle, including its own hash. This is the receiving end: run it on a bundle someone hands you.

Input parameters:

- `bundle` (object, required): An evidence bundle produced by evidence_bundle.
- `recheck_source_binding` (boolean): Re-bind Web2Json facts to the expect_source recorded in the bundle.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/dziuba0x-flario/flario#diagnostics

## Score history

- 2026-09-24: 80
- 2026-09-23: 80
- 2026-09-22: 79
- 2026-09-21: 79
- 2026-09-20: 78
- 2026-09-19: 78
- 2026-09-18: 77
- 2026-09-17: 77
- 2026-09-16: 76
- 2026-09-15: 76
- 2026-09-14: 75
- 2026-09-13: 75
- 2026-09-12: 75
- 2026-09-11: 74
- 2026-09-10: 74
- 2026-09-09: 73
- 2026-09-08: 73
- 2026-09-07: 72
- 2026-09-06: 72
- 2026-09-05: 71
- 2026-09-04: 71
- 2026-09-03: 70
- 2026-09-02: 70
- 2026-09-01: 69
- 2026-08-31: 54

## Common questions

### What is the Flario MCP server?

Flario is an MCP server listed in the public MCP registry as io.github.dziuba0x/flario. Flare for agents: FTSO prices with locally verified Merkle proofs, FDC, FAssets, x402 pay. This page covers its npm package (flario).

### Is the Flario MCP server safe to use?

Flario scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Flario MCP server expose?

Flario exposes 24 tools: get_flr_balance, get_flr_stake_info, get_ftso_feed, get_ftso_feeds_all, get_ftso_providers, and 19 more. Their descriptions and schemas cost roughly 2,490 tokens of context every time the server is loaded.

### Is the Flario MCP server still maintained?

Flario is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Flario MCP server under?

Flario declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/flario
- Socket report: https://socket.dev/npm/package/flario
- Repository: https://github.com/dziuba0x/flario
- Changelog RSS feed: https://verifymcp.io/servers/dziuba0x-flario/flario.xml
- Changelog JSON feed: https://verifymcp.io/servers/dziuba0x-flario/flario.json
- HTML version of this page: https://verifymcp.io/servers/dziuba0x-flario/flario