Finance · Remote MCP server
Luzia
Real-time crypto prices from Binance, Coinbase, Kraken, OKX, and Bybit.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.luziadev/luzia- Version
- 1.3.0
- Status
- Active
- Category
- finance
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-04-17
- Updated
- 2026-04-17
- Publisher
- luziadev (GitHub)
- Repository
- github.com/luziadev/mcp-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.luzia.dev/mcp | Authorization |
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @luziadev/mcp-server | 1.3.0 | stdio |
How to connect Luzia
Luzia is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.luzia.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The URL contains placeholders to fill in before connecting: {api_key}.
The registry entry declares an HTTP header for the connection: Authorization. clients that accept custom headers set it with the server's URL.
It can also run locally from a Node.js package published to the npm registry: @luziadev/mcp-server version 1.3.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 @luziadev/mcp-server@1.3.0. It reads the environment variable LUZIA_API_KEY (required, secret); set it 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": {
"luzia": {
"command": "npx",
"args": [
"-y",
"@luziadev/mcp-server@1.3.0"
],
"env": {
"LUZIA_API_KEY": "<secret>"
}
}
}
}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 finance servers
| Server | Runs |
|---|---|
| Lunch Money MCP (Unofficial)Read-only Lunch Money accounts, transactions, categories and budgets. Unofficial connector. | Remote · HTTP |
| Lunium — Brazilian PIX and stablecoin paymentsPIX payments for Brazil: verify a settlement with no API key, or sell USDT/USDC for BRL over PIX. | Remote · HTTP |
| luno-cms MCPLUNO — AI-era Backend Platform (not Luno crypto). BUILD/OPERATE, REGISTER/GOVERN, CONSUME. | Local · stdio |
| Luxembourg Invoices (Peppol BIS 3.0 via Storecove)Luxembourg Peppol BIS 3.0 e-invoices for AI agents: send, check recipient, get delivery proof. | Remote · HTTP |
| M2mcentX402 payment wrapper for AI Agents and MCP Servers. USDC settlements on Base L2. | Local · stdio |
| Macaroon NetworkDiscover categories, governed sources, vertical MCPs, and x402 USDC products on Macaroon Network. | Local · stdio |
| MACH Base17 Base data tools for agents over Streamable HTTP MCP. Pay per call in USDC via x402; no API key. | Remote · HTTP |
| Machine Works BrokerFree evidence capability discovery, quotes and durable unmet requests. No payment or spend. | Remote · HTTP |