MyOpenFund MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MOF_MCP_HOST | No | HTTP listen address. Default: 127.0.0.1. The Docker image sets 0.0.0.0 inside the container. | 127.0.0.1 |
| MOF_MCP_PATH | No | HTTP endpoint path; must start with /. Default: /mcp. | /mcp |
| MOF_MCP_PORT | No | HTTP port, 1-65535. Default: 8000. | 8000 |
| MOF_MCP_TOKENS | No | Comma-separated client:sha256hex[:tier] entries. Required when MOF_MCP_TRANSPORT=http; the HTTP server refuses to start without tokens. Ignored over stdio with a warning. No default. | |
| MOF_MCP_MAX_ROWS | No | Largest limit a caller may request. Default: 200. | 200 |
| MOF_MCP_TRANSPORT | No | Transport to use: stdio or http. Default: stdio. The Docker image sets http. | stdio |
| MOF_MCP_DEFAULT_ROWS | No | Rows per page when the caller gives no limit; at most MOF_MCP_MAX_ROWS. Default: 50. | 50 |
| MOF_MCP_MAX_TEXT_CHARS | No | Each error text in vault_runs_status is cut to this length. Default: 2000. | 2000 |
| MOF_VAULT_DATABASE_URL | No | Vault Postgres URL using the read-only role. Unset means no vault toolset; when set, the [vault] extra must be installed. Set sslmode explicitly: verify-full preferred, require as fallback, disable only on a trusted private network. No default. | |
| MOF_MCP_QUERY_TIMEOUT_S | No | Postgres statement_timeout per call, in seconds, 1-2147483. Default: 20. | 20 |
| MOF_MCP_MAX_RESULT_CHARS | No | Largest tool result in characters, at least 1000; larger results are refused. Default: 200000. | 200000 |
| MOF_MCP_CONNECT_TIMEOUT_S | No | Postgres connection timeout, in seconds, 2-300. Default: 10. | 10 |
| MOF_MCP_MAX_ERROR_SAMPLES | No | Error samples kept per row of vault_runs_status. Default: 5. | 5 |
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": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_infoA | What this deployment offers: enabled toolsets, your tier, version, data freshness. If the vault cannot be read, |
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 1 tool
There is only one tool, so there is no possibility of confusing it with another. Its purpose—returning deployment metadata—is clear.
With a single tool, there is no pattern to violate. The name `server_info` is clear snake_case and readable.
A one-tool surface is very thin for a server whose name suggests fund/vault operations. The sole tool only reports deployment metadata rather than exposing domain functionality.
The surface is severely incomplete for a fund-oriented MCP server: it offers no tools to read or manage vault/fund data. `server_info` is introspection only and leaves obvious domain operations missing.