Home / MCP registry index / io.flarewatch/flarewatch

io.flarewatch/flarewatch

io.flarewatch/flarewatch in the official MCP registry. Endpoint https://mcp.flarewatch.io/api/mcp. Source: github.com/nbridges333/flarewatch.

The registry describes it as: Verifiable Flare & Songbird data: validator scores, FTSO accuracy, prices, wallet intelligence.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http flarewatch https://mcp.flarewatch.io/api/mcp

{
  "mcpServers": {
    "flarewatch": {
      "url": "https://mcp.flarewatch.io/api/mcp"
    }
  }
}

code --add-mcp '{"name":"flarewatch","type":"http","url":"https://mcp.flarewatch.io/api/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

get_flare_validators get_validator_score get_ftso_providers get_ftso_provider_metrics get_network_status get_flarewatch_validator get_flarewatch_sgb_entity get_flare_prices get_recent_agent_actions get_agent_capabilities get_agent_status get_network_economics get_fassets_status get_defi_tvl get_chain_activity get_ftso_provider_history list_ftso_feeds get_payment_options simulate_delegation_rewards compare_validators compare_ftso_providers verify_response get_my_delegations get_my_claimable get_my_portfolio_summary get_my_rewards_history

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-flarewatch-flarewatch/badge.svg)](https://lazaretto.dev/mcp-registry/io-flarewatch-flarewatch)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers