Flo Blockbook MCP Server
coolboy-shivam/Flo-Blockbook-MCP-Server
Acesso a dados da blockchain FLO para agentes IA via MCP
Ver no GitHubServidor MCP que expõe as APIs do explorador Blockbook da blockchain FLO como ferramentas amigáveis para agentes de IA. Permite consultar dados da blockchain (transações, blocos, saldos de endereços) através de chamadas estruturadas em vez de parsing manual, com foco em fluxos de trabalho de consulta somente-leitura.
Instalação
npx convez-ai coolboy-shivam/Flo-Blockbook-MCP-Server1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Consultar histórico de transações de um endereço FLO
- Obter detalhes de blocos e transações específicas
- Monitorar saldo de carteiras e status de mempool
- Integrar dados blockchain em aplicações de IA
Veredito

Implementação técnica sólida de um servidor MCP para a blockchain FLO, com interface clara e bem documentada. Adequado para builders que precisam integrar dados blockchain em agentes Claude, mas com nicho específico (ecossistema FLO).
README
A tradução para o português deste README ainda está na fila.
FLO Blockbook MCP Server
An MCP server that exposes FLO Blockbook explorer APIs as AI-agent-friendly tools.
This project lets MCP-compatible clients query FLO blockchain data through structured tool calls instead of asking an assistant to scrape or manually parse explorer output. It is read-only and focused on blockchain lookup workflows such as transaction details, block details, address balances, address transaction history, latest block state, and mempool status.
Why This Exists
Blockbook already provides useful blockchain explorer APIs. MCP makes those APIs available to AI agents through a standard protocol, so an assistant can answer questions like:
Show the recent transactions for this FLO address:
FUAbBBQFNJziaSU3jVwFodsNZnAAGSCRYT
The agent can call get_address_transactions, receive structured JSON, and produce a user-facing summary.
Architecture
MCP client / AI agent
|
| stdio MCP tool calls
v
FLO Blockbook MCP server
|
| HTTPS requests
v
FLO Blockbook API
|
v
FLO blockchain data
The server uses the official MCP TypeScript SDK from Node.js and communicates over stdio, which is the common local MCP transport. It does not expose an HTTP API by default.
Tools
| Tool | Purpose |
|---|---|
get_latest_block | Fetches synced chain state and latest block metadata. |
get_block | Fetches block details by block hash or block height. |
get_transaction | Fetches transaction details by transaction id. |
get_address_balance | Fetches address balance plus spendable UTXOs. |
get_address_transactions | Fetches recent address transactions and summarizes direction, net amount, status, and confirmations. |
get_mempool | Fetches mempool sync status and current mempool size. |
All tools return both:
content: readable text for MCP clients and logs.structuredContent: JSON intended for agents and downstream automation.
Requirements
- Node.js 18 or newer.
- npm.
- Network access to a compatible Blockbook API.
The default endpoint is:
https://blockbook.flocard.app/api
Installation
git clone <repo-url>
cd <repo-folder>
npm install
Configuration
The server works without configuration. To point it at another compatible Blockbook instance, set environment variables:
export BLOCKBOOK_BASE_URL="https://blockbook.flocard.app/api"
export BLOCKBOOK_REQUEST_TIMEOUT_MS="15000"
You can also start from the included example:
cp .env.example .env
If you use .env, load it through your shell, process manager, or MCP host. This project does not load .env automatically.
Running the MCP Server
npm start
The command starts a stdio MCP server and waits silently for an MCP client. That is expected. Normal logs should not be printed to stdout because stdout is reserved for MCP protocol messages.
Quick Demo
npm run smoke
The smoke test starts the MCP server, performs an MCP handshake, lists tools, and calls live Blockbook-backed tools using this demo address:
FUAbBBQFNJziaSU3jVwFodsNZnAAGSCRYT
MCP Inspector
npm run inspect
Use the inspector to manually call tools and inspect responses.
VS Code MCP Setup
This repository includes .vscode/mcp.json for VS Code-compatible MCP clients:
{
"servers": {
"flo-blockbook": {
"type": "stdio",
"command": "node",
"args": ["${workspaceFolder}/server.js"]
}
}
}
Open the repository folder in VS Code, enable the server if prompted, and ask an agent a blockchain query. Example:
Use the FLO Blockbook MCP server to show recent transactions for FUAbBBQFNJziaSU3jVwFodsNZnAAGSCRYT
Generic MCP Client Configuration
For clients that accept JSON MCP server definitions:
{
"mcpServers": {
"flo-blockbook": {
"command": "node",
"args": ["/absolute/path/to/server.js"],
"env": {
"BLOCKBOOK_BASE_URL": "https://blockbook.flocard.app/api"
}
}
}
}
Replace /absolute/path/to/server.js with the local path to this repository's server.js.
Testing
npm run test:tools
npm run test:errors
npm test
npm run audit
The tests use the MCP protocol over stdio and make live requests to the configured Blockbook API.
Covered scenarios:
- MCP initialize handshake.
- Tool listing.
- Latest block lookup.
- Block lookup by hash and height.
- Transaction lookup.
- Address balance and UTXO lookup.
- Recent address transaction lookup.
- Mempool status lookup.
- Unknown tool error.
- Missing required arguments.
- Invalid
limitargument. - Invalid transaction and block identifiers.
Project Structure
.
├── server.js # MCP server and Blockbook API integration
├── smoke-test.js # Small end-to-end MCP demo client
├── tests/
│ ├── mcp-test-client.js # Reusable stdio MCP test client
│ ├── test-happy-paths.js # Live tool behavior tests
│ ├── test-error-paths.js # Error handling tests
│ └── test-all.js # Combined test runner
├── .vscode/mcp.json # VS Code MCP workspace config
├── .env.example # Optional environment variables
├── CONTRIBUTING.md
├── SECURITY.md
└── LICENSE
Current Limitations
- Read-only blockchain queries only.
- No transaction signing or wallet functionality.
- Uses live Blockbook data in tests, so test results depend on endpoint availability.
get_address_transactionsfetches recent transactions by resolving txids from the address endpoint and then fetching each transaction.
Contributing
Contributions are welcome. Please read CONTRIBUTING.md, run the tests, and keep tool outputs stable for MCP clients and AI agents.
Security
This server should never receive or store private keys, seed phrases, or wallet files. See SECURITY.md for details.