flare-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLARE_RPC | No | Override the mainnet RPC endpoint. | |
| X402_PAY_TO | No | Payee address receiving payments. | |
| FLARE_DA_URL | No | Override the DA-layer base URL. | |
| X402_ENABLED | No | true turns on the x402 paywall for premium tools (default: off). | |
| X402_NETWORK | No | Settlement network (default coston2; mainnet also needs X402_ALLOW_MAINNET=true). | |
| FLARE_DA_API_KEY | No | DA-layer API key; defaults to public key. | |
| FLARE_RPC_COSTON | No | Override the Coston RPC endpoint. | |
| FLARE_METRICS_API | No | Optional fallback metrics API. | |
| FLARE_PRIVATE_KEY | No | Local signing key for submitting attestation requests. Omit for prepared-only mode. | |
| FLARE_RPC_TESTNET | No | Override the Coston2 RPC endpoint. | |
| FLARE_DA_LAYER_API | No | Base URL of a Flare Data Availability Layer / indexer for historical feed results. | |
| FLARE_RPC_SONGBIRD | No | Override the Songbird RPC endpoint. | |
| X402_PRICE_DEFAULT | No | Default price in whole-token units (default 0.001). | |
| X402_TOKEN_ADDRESS | No | EIP-3009 payment token override. | |
| FLARE_PROVIDERS_API | No | An indexer endpoint returning providers JSON. | |
| FDC_VERIFIER_API_KEY | No | Verifier API key; defaults to public key 00000000-0000-0000-0000-000000000000. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_flr_balanceB | Get native FLR balance and wrapped WFLR (WNat) balance for an EVM address on Flare mainnet or Coston2 testnet. |
| get_flr_stake_infoA | 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. |
| get_ftso_feedA | Get the latest FTSO price feed (value, decimals, timestamp) for a feed by name (e.g. "FLR/USD") or raw bytes21 feed id. |
| get_ftso_feeds_allA | Get the latest FTSO price for all known feeds on the given network. |
| get_ftso_providersB | Get the list of active FTSO data providers (name, address, vote power, fee, reward rate) for the given network. |
| get_ftso_anchor_feedA | 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. |
| get_ftso_historyA | 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. |
| get_fassets_statusA | 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. |
| get_fdc_proof_statusA | Get the FDC (protocol id 200) Merkle root and finalization status for a voting round from the Flare Relay contract. |
| get_smart_account_infoA | 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. |
| fdc_request_attestationA | 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. |
| fdc_get_attestation_proofA | 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). |
| fassets_agent_statusB | 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). |
| fassets_system_stateB | 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). |
| fassets_agent_detailsA | 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. |
| fassets_liquidation_scannerA | 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. |
| fdc_bulk_proof_bundleA | 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. |
| songbird_fcc_registryC | 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. |
| fdc_web2json_requestB | 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. |
| fdc_verify_web2jsonA | 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. |
| fdc_verify_settlementA | 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. |
| fcc_deployment_statusA | 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. |
| evidence_bundleA | 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. |
| evidence_verifyA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| flare_tour | A guided, hands-on tour of Flare through live calls: a price feed, the same price carrying a Merkle proof you verify locally, and the state of FAssets. Start here if you are new to Flare. |
| verify_a_price | Fetch an FTSO price twice, once as a plain read and once carrying a Merkle proof verified locally against the on-chain root, and explain exactly what the difference buys you. |
| prove_a_web_fact | Use FDC Web2Json to make any public HTTP endpoint into something a smart contract can verify, and learn why binding the proof to an expected source is the whole game. |
| fassets_health_check | Read live FAssets state and agent collateral on Flare and summarise where the risk sits, using real numbers rather than a description of how FAssets works. |
| prove_what_you_acted_on | Bundle the facts behind a decision into something a third party can verify without trusting the agent, then try to forge it and watch the verification catch you. |
| watch_flare_2_rollout | Read the confidential-compute deployment straight off the chain — which networks have it, what it can do, what it is wired to — while the rollout is still in progress and before Flare has published an ABI. |
| why_flare_for_agents | The honest case for and against building agent infrastructure on Flare, grounded in live calls rather than the marketing site. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| flare-feeds | List of known FTSO price feeds on Flare (feed id, name, category). |
| flare-contracts | Flare ContractRegistry address and instructions for resolving contract addresses at runtime. |
TDQS
Scored across 24 tools
Most tools serve clearly distinct purposes, but there is real overlap: get_fassets_status is largely superseded by fassets_system_state, get_flr_balance is a subset of get_flr_stake_info, and get_ftso_feed versus get_ftso_anchor_feed are easy to confuse without reading descriptions. The detailed descriptions help, but the boundaries are not always crisp.
The set is consistently snake_case, but the naming pattern is mixed: some tools start with get_, others use domain prefixes like fdc_/ fassets_/ evidence_, and songbird_fcc_registry does not follow a verb pattern at all. Word order also varies, such as fdc_web2json_request versus fdc_request_attestation.
24 tools is at the heavy end of the acceptable range, and the server covers several protocol families rather than one focused workflow. Each family has useful tools, but the broad scope and near-redundant status/balance tools make the set feel slightly bloated.
Core workflows are well covered: reading state, requesting and retrieving FDC proofs, verifying proofs against the on-chain Relay root, and bundling evidence for downstream verification. Minor gaps exist, such as no dedicated generic verifier for Payment or AddressValidity attestations, but agents can work around them.