Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.flarewatch/flarewatch

REMOTE · MCP.FLAREWATCH.IO · 2 COMPONENTS

Verifiable Flare & Songbird data: validator scores, FTSO accuracy, prices, wallet intelligence.

0 this week 86 Trust /100

Last scanned (13 hours ago)

Scores higher than 88% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security83
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability86
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 2365 tokens (~78/item across 30 items; 26 tools + 4 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 26 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 28 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 2 Nov 26 0
    • Tool “get_flarewatch_validator” rewrote its description, which is the text the model reads security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.flarewatch.io/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.flarewatch.io CN=YR2,O=Let's Encrypt,C=US 2 Oct 2026 31 Dec 2026 RSA 2048 SHA256-RSA 6655b8a1d75a71f7efe8d4771294eda55aa
SANs: mcp.flarewatch.io
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.flarewatch.io. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
flarewatch.io. DS published 2371 13 Verified
mcp.flarewatch.io. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; upgrade-insecure-requests; script-src 'self' 'unsafe-eval' 'unsafe-inline' https://s3.tradingview.com https://*.tradingview.com https://va.vercel-scripts.com https://static.cloudflareinsights.com https://www.googletagmanager.com https://*.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https: blob:; font-src 'self' data:; connect-src 'self' https://www.flarewatch.io https://cloudflareinsights.com https://rpc.flarewatch.io wss://rpc.flarewatch.io https://flare-api.flare.network wss://flare-api.flare.network https://songbird-api.flare.network wss://songbird-api.flare.network https://flare-explorer.flare.network https://api.flaremetrics.io https://raw.githubusercontent.com https://api.coingecko.com https://api.web3modal.org https://pulse.walletconnect.org https://pulse.walletconnect.com https://explorer-api.walletconnect.com wss://relay.walletconnect.org wss://relay.walletconnect.com https://portal.flare.network https://*.tradingview.com wss://*.tradingview.com ws
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy accelerometer=(), autoplay=(), browsing-topics=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(), geolocation=(), gyroscope=(), interest-cohort=(), keyboard-map=(), magnetometer=(), microphone=(), midi=(), payment=(), picture-in-picture=(self "https://*.tradingview.com" "https://*.tradingview-widget.com"), publickey-credentials-get=(self), screen-wake-lock=(), sync-xhr=(), usb=(), web-share=(), xr-spatial-tracking=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.flarewatch.io/api/mcp Verified 200
http (plaintext) http://mcp.flarewatch.io/api/mcp HTTPS enforced 308 https://mcp.flarewatch.io/api/mcp
MCP tools · 26 exposed · ~2,197 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_ftso_providers ~92

Side-by-side comparison of up to 10 FTSO providers on Flare or Songbird. Rows returned in the order supplied (no re-ranking by FlareWatch). Flare rows include the composite Score; Songbird rows expose vote power, fee, last-epoch reward rate. Missing addresses return found=false with null fields.

NameTypeReqDescription
addressesarrayyes–
networkstringyes–

No output schema declared.

No examples provided.

compare_validators ~78

Side-by-side comparison of up to 10 Flare validators by NodeID. Rows returned in the order supplied (no re-ranking by FlareWatch). Each row carries score, stake, fee, uptime, capacity, APR, and stake-period expiry. Missing NodeIDs return found=false with null fields.

NameTypeReqDescription
node_idsarrayyes–

No output schema declared.

No examples provided.

get_agent_capabilities ~86

Return the FlareWatch agent's capability surface: autonomous-vs-total playbook counts per family (validator families are propose-only — autonomous 0 by design), autonomous fraction across agent-owned surfaces, drill correctness, defects caught, and recovery counts (deterministic = the node's own controllers; agentic = the agent). Source: hourly signed snapshot; available=false when unavailable.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_agent_status ~86

Return the FlareWatch agent's reliability scorecard from its hourly signed snapshot: autonomous fraction across agent-owned surfaces (validator families are propose-only) + per-family breakdown, recovery counts (deterministic = the node's own controllers; agentic = the agent; 30-day window), drill correctness, defects caught, and human-in-the-loop queue depth. available=false when unavailable.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_chain_activity ~73

Return live Flare C-chain activity: transactions per second, average block time, block utilization, gas price (gwei), average fee per tx, latest block number, and all-time totals (transactions, addresses, blocks). Source is a live block sample plus explorer stats. Nulls returned when a leg is unavailable.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_defi_tvl ~66

Return total value locked (USD) across the Flare DeFi ecosystem with a per-protocol breakdown (protocol name, TVL, token count). Source is on-chain reads valued at current prices. available=false / total null when the price-dependent TVL read is unavailable.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_fassets_status ~80

Return FAssets status on Flare: for each FAsset (e.g. FXRP), its symbol, underlying asset, minted amount, and USD TVL (minted x underlying price), plus aggregate total_tvl_usd. Source is on-chain totalSupply reads valued at current prices. available=false when the read fails or none are minted.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_flare_prices ~120

Latest FLR, SGB and XRP prices in USD and major fiats (EUR, GBP, AUD, JPY, CAD). Each asset has its OWN source (ftso oracle, or coingecko fallback) and sources can differ within one response, so check source per asset. degraded=true only when a whole upstream fails: one asset falling back does NOT set it, nor a missing rate (fx.<cur>=null). fx is the shared USD-to-fiat rate: fiat = usd * fx.

NameTypeReqDescription
currenciesarray––

No output schema declared.

No examples provided.

get_flare_validators ~78

List Flare P-Chain validators with FlareWatch composite Score, stake, fee, uptime, and capacity. Sort by score (default), stake, or apy. Pure on-chain + computed data; no editorial ranking. limit caps at 100.

NameTypeReqDescription
limitinteger––
sort_bystring––

No output schema declared.

No examples provided.

get_flarewatch_sgb_entity ~86

Return FlareWatch's Songbird FTSO entity's live on-chain stats: WSGB vote power, self-balance, current delegation fee, and per-WSGB reward rate from the last finished reward epoch. Source is direct on-chain reads (WNat + WNatDelegationFee + RewardManager). configured=false indicates the entity address isn't set yet.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_flarewatch_validator ~81

Return FlareWatch's own Flare P-Chain validators — same scoring algorithm as every other validator, no promotional weighting. One row per node (label, self-bond, delegations, stake count, fee, uptime, expiry, Score) plus entity totals. is_live=false marks a cold-load fallback row whose live figures are not measurements.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_ftso_provider_history ~81

Return one Flare FTSO provider's per-epoch reward-rate and Score trend over the last tracked reward epochs (up to 30, newest first). address may be the provider's entity address or its delegation address. found=false when the provider isn't in the tracked window.

NameTypeReqDescription
addressstringyes–
limitinteger––

No output schema declared.

No examples provided.

get_ftso_provider_metrics ~102

Return detailed metrics for one FTSO data provider on Flare or Songbird: fee, reward rate, uptime, vote power, delegator count, and (Flare) the FlareWatch composite Score plus the provider's rank and percentile by score and by reward rate among all providers (provider_count is the denominator). address must be a lowercase 0x EVM address.

NameTypeReqDescription
addressstringyes–
networkstringyes–

No output schema declared.

No examples provided.

get_ftso_providers ~93

List FTSO data providers on Flare or Songbird. Flare rows include FlareWatch composite Score; Songbird rows expose vote power, fee, and last-epoch reward rate (no score on SGB by design). Default sort: score (FLR) / vote power (SGB). limit caps at 100.

NameTypeReqDescription
limitinteger––
networkstringyes–

No output schema declared.

No examples provided.

get_my_claimable ~79

Return what the calling wallet can claim right now: Flare FTSO delegation, P-chain staking (mirror), provider fee and validation rewards in FLR, the unclaimed epoch range, and Songbird FTSO rewards. Types owed but not yet priced on-chain are listed in flr_pending_resolution. Requires OAuth scope wallet:read.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_my_delegations ~60

Return the calling wallet's WFLR FTSO delegations and P-chain validator delegations. Requires OAuth scope wallet:read. The wallet is resolved from the OAuth token; no input arg accepts a wallet address (cross-tenancy isolation).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_my_portfolio_summary ~63

Return the calling wallet's FLR and SGB balances and their USD valuations. Native and wrapped (WFLR / WSGB) balances are reported separately; wrapped balances roll into the per-token USD values and the total. Requires OAuth scope wallet:read.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_my_rewards_history ~73

Return the calling wallet's reward history: FLR claimed per recent reward epoch (at least the last 30 days), split into FTSO delegation, P-chain staking and provider fee (including auto-claims), plus cumulative validation rewards and burn-window countdowns. Read-only. Requires OAuth scope wallet:read.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_network_economics ~95

Return Flare's monetary metrics: circulating and committed supply, total staked, staking ratio, WFLR supply, annualized inflation (rate + FLR/yr), and the FLR burn rate (daily + annualized estimate) with net supply change. Source is on-chain reads plus a live block sample for the burn estimate. Nulls (not zeros) returned for any leg whose on-chain read fails.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_network_status ~76

Return current FTSO reward-epoch state for Flare (default) or Songbird: current epoch ID, when it started, how far into the epoch we are, and how many seconds remain. Source is FlareSystemsManager on-chain reads. Nulls returned when on-chain read fails.

NameTypeReqDescription
networkstring––

No output schema declared.

No examples provided.

get_payment_options ~67

Return machine-readable payment options for paid FlareWatch capacity: deposit USDT0 on Flare and the sending wallet is credited compute units (CU) that never expire. Includes the deposit address, credit rate, and balance URL. provisioned=false means the rail is not accepting deposits yet.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_recent_agent_actions ~111

Return the FlareWatch agent's recent action feed: surface, action kind (observation/propose/topup/rollback/claim/etc), outcome, and detect-to-remediate latency on the agent's own recoveries. Validator-surface entries are proposals only — the node's own controllers act, never the agent. Source: hourly signed snapshot, verifiable via chain_verify_url; available=false when it is unavailable.

NameTypeReqDescription
limitinteger––
since_ts_minutestring––

No output schema declared.

No examples provided.

get_validator_score ~74

Return the FlareWatch composite Score and full per-dimension breakdown for one Flare validator by NodeID. Each dimension carries its raw score, max, and the detail string explaining the score (e.g. 'Active outage · 3 consecutive missed epochs'). Methodology link returned.

NameTypeReqDescription
node_idstringyes–

No output schema declared.

No examples provided.

list_ftso_feeds ~102

List the FTSO block-latency price feeds Flare's oracle provides (e.g. FLR/USD, BTC/USD, ETH/USD) with Flare's published risk tier for each (low/medium/high/new — volatility + liquidity). Optionally filter by risk. These are the symbols the on-chain oracle prices; this tool returns the feed list, not live prices.

NameTypeReqDescription
limitinteger––
riskstring––

No output schema declared.

No examples provided.

simulate_delegation_rewards ~121

Estimate annual WFLR FTSO-delegation rewards for delegating an amount to a Flare FTSO provider (defaults to FlareWatch). Annualizes the provider's latest realized per-epoch reward rate (rate x ~104.29 epochs/yr). Returns estimated APR and annual/monthly reward in FLR. A projection, not a guarantee; FTSO delegation only, not P-chain staking. found=false when the provider isn't cached.

NameTypeReqDescription
amount_flrnumberyes–
provider_addressstring––

No output schema declared.

No examples provided.

verify_response ~74

Verify that a previously-served FlareWatch MCP response really came from this server. Pass the structured envelope WITHOUT the verification_signature field as payload, and the signature you received as signature. Returns valid=true when the HMAC matches. Useful for cross-AI citation verification.

NameTypeReqDescription
payload–yes–
signaturestringyes–

No output schema declared.

No examples provided.

Install

How do I install the io.flarewatch/flarewatch MCP server?

io.flarewatch/flarewatch is a hosted endpoint at https://mcp.flarewatch.io/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.flarewatch.io

# add to Claude Code
claude mcp add --transport http io-flarewatch-flarewatch 'https://mcp.flarewatch.io/api/mcp'
Common questions

What is the io.flarewatch/flarewatch MCP server?

io.flarewatch/flarewatch is an MCP server listed in the public MCP registry as io.flarewatch/flarewatch. Verifiable Flare & Songbird data: validator scores, FTSO accuracy, prices, wallet intelligence. This page covers its hosted endpoint (https://mcp.flarewatch.io/api/mcp).

Is the io.flarewatch/flarewatch MCP server safe to use?

io.flarewatch/flarewatch scores 86 out of 100 on VerifyMCP. 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 io.flarewatch/flarewatch MCP server expose?

io.flarewatch/flarewatch exposes 26 tools: get_flare_validators, get_validator_score, get_ftso_providers, get_ftso_provider_metrics, get_network_status, and 21 more. Their descriptions and schemas cost roughly 2,197 tokens of context every time the server is loaded.

Does the io.flarewatch/flarewatch MCP server require authentication?

No. We connected to io.flarewatch/flarewatch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.flarewatch/flarewatch MCP server still maintained?

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

What did VerifyMCP test on the io.flarewatch/flarewatch MCP server?

VerifyMCP ran 13 checks on io.flarewatch/flarewatch, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.