Other · Local MCP server
Flario
Flare for agents: FTSO prices with locally verified Merkle proofs, FDC, FAssets, x402 pay.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.dziuba0x/flario- Version
- 1.6.0
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-01
- Updated
- 2026-09-01
- Publisher
- dziuba0x (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/dziuba0x) · how
- Website
- github.com/dziuba0x/flario#readme
- Repository
- github.com/dziuba0x/flario
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | flario | 1.6.0 | stdio |
How to connect Flario
Flario runs locally from a Node.js package published to the npm registry: flario version 1.6.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y flario@1.6.0. It reads these environment variables: FLARE_RPC, FLARE_RPC_TESTNET, FLARE_PRIVATE_KEY (secret) and X402_ENABLED; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"flario": {
"command": "npx",
"args": [
"-y",
"flario@1.6.0"
],
"env": {
"FLARE_RPC": "<value>",
"FLARE_RPC_TESTNET": "<value>",
"FLARE_PRIVATE_KEY": "<secret>",
"X402_ENABLED": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Flamel Public ContentRead-only MCP server for Flamel.ai's public content: company overview, blog, case studies, FAQs. | Remote · HTTPLive check: ✓ handshake |
| FlameoxBounded local runtime evidence from explicit artifacts and typed direct targets. | Local · stdio |
| FlareoracleFlareOracle - 12 Flare tools: FTSO oracles, FAssets, state connector, FXRP, FlareDrops. | Remote · HTTPLive check: ✓ handshake |
| FlareSignal IntelligenceFlare and Songbird intelligence with provenance, source health, MCP access and x402 readiness. | Remote · HTTPLive check: ✗ no handshake |
| FlashSpaced-repetition flashcards your AI writes, quizzes you on by voice, and schedules with FSRS. | Remote · HTTPLive check: sign-in required |
| Flash Props ApiFlash Props API: player-prop analysis, projections, evidence, and line movement over REST/MCP. | Remote · HTTPLive check: ✓ handshake |
| Flato Design MCPConnect AI agents to Flato's editable canvas runtime through a hosted MCP server. | Remote · HTTPLive check: sign-in required |
| FleetpostA mailbox for your machines: read fleet capabilities, send a request. Offline, no server. | Local · stdio |