Finance · Remote MCP server
Orla
Personal, family and business books over fiat and crypto. Reads and records; it cannot pay.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
finance.orla/orla- Version
- 0.3.0
- Status
- Active
- Category
- finance
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-19
- Updated
- 2026-09-19
- Publisher
- finance.orla
- Namespace
- Namespace verified by the MCP Registry via the domain orla.finance · how
- Website
- orla.finance/en/ai-agents/api
- Repository
- github.com/cheetah-trade/orla-cli
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app.orla.finance/api/mcp/personal | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | orla-cli | 0.3.0 | stdio |
How to connect Orla
Orla is a remote MCP server: there is nothing to install. Its endpoint is https://app.orla.finance/api/mcp/personal, 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.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: orla-cli version 0.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 orla-cli@0.3.0.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"orla": {
"command": "npx",
"args": [
"-y",
"orla-cli@0.3.0"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. 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 |
|---|---|
| Orchard Data MCPPay-per-call market data for AI agents via x402 (USDC on Base): regime, track record, catalysts. | Local · stdio |
| OrdinalsBitcoin Ordinals MCP Server - inscriptions, runes, BRC-20, collections & rare sats. | Local · stdio |
| OrganizzeYour Organizze finances in natural language: consolidated balances, monthly overview, transaction se. | Remote · HTTPLive check: ✓ handshake |
| Origami EntreprisesFrench company data: financials, dirigeants, BODACC, INPI filings, PEP checks, alerts. | Remote · HTTPLive check: sign-in required |
| OrphographAnchor a file's SHA-256 fingerprint to Bitcoin. The file never leaves the device. | Local · stdio |
| Oshyn Free AI-Powered Website ToolsFree AI-powered DXP tools by Oshyn: GEO & Reliability scan, Choose New DXP and Estimate DXP Budget. | Remote · HTTPLive check: ✓ handshake |
| Osigu RCMGerencie cobranças, invoices e atendimentos do RCM da Osigu diretamente do seu agente de IA. | Remote · HTTPLive check: ✗ no handshake |
| Otskit MCPStamp, upgrade, and verify Bitcoin timestamps via AI agents. No API keys required. | Local · stdio |