Finance MCP Aggregator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | Port to use when MCP_TRANSPORT is set to 'http'. | 8000 |
| MCP_TRANSPORT | No | Transport to use for the MCP server. Use 'stdio' (default) or 'http'. | stdio |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_finance_categoriesA | List the domains of finance tools available (market data, portfolio analysis, risk analysis, technical analysis, fundamental analysis, currency/crypto) along with how many tools live in each. |
| search_finance_toolsA | Find the finance tools most relevant to a natural-language request. Call this FIRST before execute_finance_tool. It searches across all 43 registered finance tools (market data, portfolio analysis, risk, technical analysis, fundamentals, currency/crypto) and returns only the ones relevant to your query, each with its name, description and the parameters it expects -- so you never need the full tool catalog in context at once. |
| get_tool_schemaA | Get the exact parameter schema for a single named finance tool (use after search_finance_tools has told you the tool name). |
| execute_finance_toolA | Execute a specific finance tool by name with the given parameters. Always call search_finance_tools or get_tool_schema first to confirm the correct tool name and parameter shape -- this avoids parameter hallucination from guessing at an unseen schema. |
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 4 tools
Each tool has a distinct role: listing categories, searching for tools, fetching schemas, and executing. There is no functional overlap between any two tools.
All tool names follow a consistent verb_noun pattern (list_finance_categories, search_finance_tools, get_tool_schema, execute_finance_tool), making the API predictable and easy to navigate.
With only 4 tools, the server is well-scoped for its aggregator purpose. Instead of exposing 43 tools directly, it provides a lean meta-layer that is easy to learn and use.
The tool set covers the full discovery-to-execution workflow: list categories, search, get schema, and execute. There are no obvious missing operations for an aggregator that intentionally hides the underlying tool catalog.