vfat Metrics MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP_HOST | No | HTTP bind address when using HTTP transport. | 127.0.0.1 |
| MCP_HTTP_PORT | No | HTTP port when using HTTP transport. | 3000 |
| MCP_TRANSPORT | No | Transport mode: 'stdio' or 'http'. | stdio |
| VFAT_METRICS_API_URL | No | Upstream base URL for the vfat Metrics API. | https://info-api.vf.at |
| VFAT_METRICS_TIMEOUT_MS | No | Request timeout in milliseconds. | 15000 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_vfat_positionsA | Returns all current vfat/Sickle positions reported for an EVM admin address, including provider metrics and underlying position fields. |
| get_vfat_positionA | Finds a single position by NFT/token ID among the positions reported for an EVM admin address. |
| get_vfat_portfolio_summaryA | Returns a compact cross-chain position count, protocol breakdown, range status and provider-derived USD totals for an EVM admin address. |
| get_vfat_position_actionsA | Returns transaction-grouped lifecycle actions for one vfat/Sickle NFT position, including deposits, rebalances, cashflows, token deltas, dust, rewards and swaps. |
| get_vfat_position_value_historyA | Returns a chronological time series of position value, normalized underlying token balances and in-range status across NFT migrations and rebalances. |
| get_vfat_position_performanceA | Returns a chronological APR, ROI, PnL, realized PnL and balance time series for one vfat/Sickle NFT position. |
| export_vfat_position_csvA | Exports transaction actions, position value history or performance history as RFC-style CSV text for reproducible analysis. |
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
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- 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/Raumberg/vfat-metrics-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server