tefas-fund-comparator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| 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_fundsA | List TEFAS funds by type and optional date range / filters. Pulls general fund information (code, name, price, AUM, investors) from TEFAS via pytefas. By default returns a snapshot of the latest available day in the range (one row per fund). |
| get_fund_detailsA | Get general info, optional price history, and portfolio allocation for a fund. Resolves the fund code (and type if omitted), returns a summary of latest price / AUM / investors, period return, recent price history, and latest asset allocation. |
| compare_fundsA | Compare multiple TEFAS funds on return, risk, and size metrics. Fetches price history for each code and computes selected metrics: cumulative/annualized return, volatility, Sharpe ratio, max drawdown, latest AUM, and investor count. |
| get_portfolio_breakdownA | Get asset allocation (portfolio breakdown) for a TEFAS fund. Returns holdings percentages such as stocks, reverse repo, eurobonds, government bonds, precious metals, foreign assets, etc. (whatever TEFAS publishes for that fund on the selected date). |
| get_historical_returnsA | Fetch TEFAS return tables by ranking basis (RB / SB / MB). Uses tefasfon to pull TEFAS comparative return data:
|
| analyze_performanceA | Analyze risk/return statistics for one or more TEFAS funds. Computes for each fund (from daily price history):
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/merkezekre2026/tefas-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server