finary-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| finary_meA | Read the authenticated Finary profile. Does not modify Finary. |
| finary_organizationsB | List Finary organizations available to the authenticated user. |
| finary_institution_connectionsA | List connected financial institutions and their connection status. |
| finary_portfolioB | Read a portfolio class: investments, securities, cryptos, fonds_euro, scpis, real_estates, or holdings_accounts. |
| finary_transactionsB | Read transactions for checking, investment, or credit accounts with optional filters. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool addresses a clearly distinct domain: user profile, organizations, institution connections, portfolio classes, and transactions. No overlap in purpose, and the descriptions make the boundaries obvious.
All tools use a consistent 'finary_' prefix followed by a descriptive noun (me, organizations, institution_connections, portfolio, transactions). The naming pattern is uniform and predictable.
Five tools is well-scoped for a read-only financial data API. Each tool covers a major data category without redundancy, and the count is neither sparse nor bloated.
The surface covers the core read operations for a personal finance platform: user, orgs, connections, portfolio, and transactions. Minor gaps exist, such as no detailed per-asset breakdown beyond portfolio class, but the essential workflows are supported.