finanal-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FMP_API_KEY | Yes | Your Financial Modeling Prep API key (free tier, 250 req/day) | |
| TAVILY_API_KEY | Yes | Your Tavily API key (free tier, 1,000 credits/month) | |
| TAPETIDE_API_KEY | Yes | Your Tapetide API token (free from settings) |
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 |
|---|---|
| search_recipesA | Search previously solved Q&A recipes. ALWAYS call this FIRST before search_apis or call_api. If a matching recipe exists (score < -1.0 is a strong match), return it directly without further API calls. |
| search_apisA | Search API endpoints across fmp, tapetide, and tavily. Source routing: tapetide=India NSE/BSE, fmp=US/global stocks, tavily=all news. Pass source='tapetide'|'fmp'|'tavily' to restrict. Returns slim rows (id, source, path, summary, score) — call get_api_details for full schema. |
| get_api_detailsB | Get full metadata/schema for an endpoint by id. |
| search_docsC | Search synthetic/ingested docs with BM25. |
| call_apiB | Call a live API endpoint by endpoint_id and params. |
| save_recipeC | Save a solved recipe to cache. |
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 6 tools
Each tool has a clear, distinct purpose: call_api vs get_api_details separate invocation from metadata, search tools target different data types (APIs, docs, recipes), and save_recipe is uniquely for caching solved queries. No ambiguity between tools.
All tool names follow a consistent verb_noun pattern with snake_case: call_api, get_api_details, save_recipe, search_apis, search_docs, search_recipes. No mixed conventions.
6 tools is ideal for a server that provides search, details, and invocation across multiple data sources. Each tool earns its place without being overly narrow or broad.
The set covers the full workflow: search for APIs, get details, call them, search docs, and reuse saved recipes. Minor gap: no explicit tool to list all endpoints or manage recipes beyond saving, but core functionality is complete.