Is the Flarewatch MCP server down?

mcp-registry/io.flarewatch/flarewatch · v0.2.0

healthy
Last checked 2026-10-18 13:22 UTC · handshake 434ms

As of 2026-10-18 13:22 UTC, the Flarewatch MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
100%
checks observed
3,706
outages (90d)
1
tools
26

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

Install Flarewatch MCP server

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "flarewatch-mcp-server": {
      "type": "http",
      "url": "https://mcp.flarewatch.io/api/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (83/100)

B (83/100): 0 error(s), 4 warning(s) across 26 tool(s); ~4,028 tokens of tool definitions.
Scores higher than 42% of 15,375 MCP servers Glimind has audited.
Its tool list costs an agent ~4,028 tokens per session — more than 55% of servers.
83 → 83 since 2026-10-17
no tool-poisoning patterns
Schemas88
Descriptions55
Safety hints100
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability90

What to fix (5)

22 parameter(s) across 13 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: compare_ftso_providers, compare_validators, get_flare_prices, get_flare_validators, get_ftso_provider_history and 8 more

1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: verify_response

Handshake + tools/list takes ~2,414 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

In the last 30 days: 1 tool(s) removed and 0 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 13 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.flarewatch%2Fflarewatch/fixes

verify_response 1 change 
{
  "name": "verify_response",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "payload",
      "signature"
    ],
    "properties": {
      "payload": {
        "type": "string"
      },
      "signature": {
        "type": "string",
        "maxLength": 256,
        "minLength": 32
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "title": "Verify Response",
    "readOnlyHint": true,
    "openWorldHint": true
  },
  "title": "Verify Response"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.flarewatch/flarewatch"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.flarewatch/flarewatch"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.flarewatch%2Fflarewatch.svg)](https://glimind.com/server/mcp-registry%2Fio.flarewatch%2Fflarewatch?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.flarewatch%2Fflarewatch?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.flarewatch%2Fflarewatch.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.flarewatch%2Fflarewatch.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.flarewatch%2Fflarewatch?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b1314ff0ca59cd7e…, first seen 2026-10-17, included at leaf 16351 of 22,054. Version history · verify what your client received.

Tools (26)

Compare: most reliable data servers · most reliable finance servers · most reliable security servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Flarewatch MCP server down right now?

As of 2026-10-18 13:22 UTC, the Flarewatch MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

How many tools does Flarewatch MCP server provide?

Flarewatch MCP server advertises 26 tools, including compare_ftso_providers, compare_validators, get_agent_capabilities, get_agent_status, get_chain_activity.

How do I install Flarewatch MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.flarewatch.io/api/mcp

Is the Flarewatch MCP server safe to connect to an AI agent?

Glimind scanned all 26 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Flarewatch MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.