lurq

MCP server

Home

FlareSignal Intelligence

Flare and Songbird intelligence with provenance, source health, MCP access and x402 readiness.

Endpoint
Answering
Works in
20 of 21 clients
Tools
59
Last checked
Sep 18, 2026

Does FlareSignal Intelligence work in your MCP client?

Registry name io.flaresignal/intelligence, endpoint https://flaresignal.io/wp-json/flaresignal/v1/mcp.

  • Claude Codeworks
  • Claude Desktopworks
  • Claude.aiworks
  • Claude API MCP connectorworks
  • ChatGPTworks
  • OpenAI Responses APIworks
  • Codexworks
  • Gemini CLIworks
  • Cursorworks
  • VS Code (GitHub Copilot)works
  • Windsurf (Devin Desktop)works
  • Zedworks
  • JetBrains AI Assistantworks
  • Junieunknownno source confirms Junie supports Streamable HTTP
  • Clineworks
  • Continueworks
  • Gooseworks
  • Lovableworks
  • Replit Agentworks
  • Bolt.newworks
  • v0works

How clients sign in

No credentials: it answered lurq's probe without any.

Tools

flaresignal.agent.access.catalogflaresignal.agent.brief.queryflaresignal.agent.ontology.getflaresignal.agent.planflaresignal.agent.questions.catalogflaresignal.agent.researchflaresignal.agent.research.traceflaresignal.agent.session.createflaresignal.agent.session.getflaresignal.agent.task.contractflaresignal.agent.task.getflaresignal.agent.task.submitflaresignal.agent.task.traceflaresignal.analytics.catalogflaresignal.analytics.metric.contextflaresignal.composed.catalogflaresignal.composed.queryflaresignal.composed.synthesis.catalogflaresignal.composed.synthesis.queryflaresignal.discovery.a2a.getflaresignal.discovery.capabilities.getflaresignal.discovery.capabilities.listflaresignal.discovery.catalogflaresignal.discovery.datasets.getflaresignal.discovery.datasets.listflaresignal.discovery.distribution.getflaresignal.discovery.inventory.queryflaresignal.discovery.metrics.catalogflaresignal.discovery.metrics.searchflaresignal.discovery.parity.getflaresignal.discovery.searchflaresignal.discovery.surfaces.getflaresignal.discovery.surfaces.listflaresignal.events.archive.queryflaresignal.events.live.queryflaresignal.flow_atlas.streamflaresignal.history.availability.queryflaresignal.history.coverage.queryflaresignal.history.intelligence.queryflaresignal.intelligence.catalog.getflaresignal.market.executions.latestflaresignal.market.history.queryflaresignal.market.truth.liveflaresignal.metrics.history.queryflaresignal.metrics.live.queryflaresignal.opportunities.catalogflaresignal.opportunities.gapsflaresignal.opportunities.metric_mapflaresignal.opportunities.scenarioflaresignal.opportunities.searchflaresignal.payment.x402.canaryflaresignal.products.catalogflaresignal.products.commercialflaresignal.products.executeflaresignal.products.searchflaresignal.products.specflaresignal.products.usageflaresignal.sources.health.queryflaresignal.surface.invoke

Get the setup for your client from your agent

This page is a daily snapshot. lurq's connect_check answers for the client you are wiring this server into, with the exact steps and the config to paste in that client's own format, and lurq mcp-pin tells you when the server changes. One command connects Claude Code, Cursor, VS Code and other agents:

npx lurqrun

Free to start. How connect_check works

From lurq's credential-free probe of this server's endpoint on Sep 18, 2026, and each client's own documentation. This page refreshes every 24 hours. How the probe works, and how maintainers opt out.