ManifoldBT Docs is an MCP server published by com.manifoldbt, hosted at mcp.manifoldbt.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 4 tools, including search_docs, explain_error, get_capabilities, list_topics.
Docs for writing manifoldbt backtests: DSL rules, signatures, examples and error fixes.
Nothing else in the archive shares these values.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
Search the manifoldbt documentation: DSL rules and pitfalls, indicator and API signatures, config fields, execution semantics (which price a stop or target fills at, which fee each fill pays, what a reversal counts as, which ddof an indicator uses), how to read result metrics honestly, and worked examples. Ask in natural language ('how do I reference another symbol', 'what happens when a bar gaps through my stop', 'is this Sharpe meaningful') or by name ('symbol_ref', 'warmup_bars'). Pass a result's exact title to read that chunk again. A chunk already sent in this session is not sent again.
| Parameter | Type | Description |
|---|---|---|
| limit | integer | |
| query * | string |
{
"name": "search_docs",
"description": "Search the manifoldbt documentation: DSL rules and pitfalls, indicator and API signatures, config fields, execution semantics (which price a stop or target fills at, which fee each fill pays, what a reversal counts as, which ddof an indicator uses), how to read result metrics honestly, and worked examples. Ask in natural language ('how do I reference another symbol', 'what happens when a bar gaps through my stop', 'is this Sharpe meaningful') or by name ('symbol_ref', 'warmup_bars'). Pass a result's exact title to read that chunk again. A chunk already sent in this session is not sent again.",
"inputSchema": {
"type": "object",
"title": "search_docsArguments",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"title": "Limit",
"default": 5
},
"query": {
"type": "string",
"title": "Query"
}
}
},
"outputSchema": {
"type": "object",
"title": "search_docsDictOutput",
"additionalProperties": true
}
}Explain an error returned by the manifoldbt engine: what it means, what caused it, and how to fix it. Paste the message verbatim. Use this before changing code in response to an engine error -- these messages name a rule rather than the mistake, and guessing wastes a round trip.
| Parameter | Type | Description |
|---|---|---|
| message * | string |
{
"name": "explain_error",
"description": "Explain an error returned by the manifoldbt engine: what it means, what caused it, and how to fix it. Paste the message verbatim. Use this before changing code in response to an engine error -- these messages name a rule rather than the mistake, and guessing wastes a round trip.",
"inputSchema": {
"type": "object",
"title": "explain_errorArguments",
"required": [
"message"
],
"properties": {
"message": {
"type": "string",
"title": "Message"
}
}
},
"outputSchema": {
"type": "object",
"title": "explain_errorDictOutput",
"additionalProperties": true
}
}Which manifoldbt version this documentation covers, and which of the THREE licence tiers each feature needs. Check before writing code around sweeps, walk-forward, cross-exchange, the GPU or the tick layer: the first three refuse on Community, the last two on anything below Researcher -- and the two Researcher gates raise different exception types.
No parameters.
{
"name": "get_capabilities",
"description": "Which manifoldbt version this documentation covers, and which of the THREE licence tiers each feature needs. Check before writing code around sweeps, walk-forward, cross-exchange, the GPU or the tick layer: the first three refuse on Community, the last two on anything below Researcher -- and the two Researcher gates raise different exception types.",
"inputSchema": {
"type": "object",
"title": "get_capabilitiesArguments",
"properties": {}
},
"outputSchema": {
"type": "object",
"title": "get_capabilitiesDictOutput",
"additionalProperties": true
}
}START HERE. Returns a complete, runnable backtest script (open a store, strategy, config, fees, run, read the metrics) plus the stateful-band, bracket-exit, higher-timeframe, cross-asset and state-filter (scan(): HMM, Kalman, any recursion) variants -- then the list of rules the engine enforces and of what a fill actually does (which fee a stop pays, where a gapped bracket fills, what a reversal counts as). One call replaces the eight searches every first script otherwise needs.
No parameters.
{
"name": "list_topics",
"description": "START HERE. Returns a complete, runnable backtest script (open a store, strategy, config, fees, run, read the metrics) plus the stateful-band, bracket-exit, higher-timeframe, cross-asset and state-filter (scan(): HMM, Kalman, any recursion) variants -- then the list of rules the engine enforces and of what a fill actually does (which fee a stop pays, where a gapped bracket fills, what a reversal counts as). One call replaces the eight searches every first script otherwise needs.",
"inputSchema": {
"type": "object",
"title": "list_topicsArguments",
"properties": {}
},
"outputSchema": {
"type": "object",
"title": "list_topicsDictOutput",
"additionalProperties": true
}
}Reference documentation for the manifoldbt backtesting library. CONSULT THIS BEFORE WRITING ANY manifoldbt CODE OR DSL EXPRESSION, and whenever the engine returns an error: the DSL has its own rules, and code written from memory breaks on them one compiler error at a time. Call list_topics FIRST: it returns a complete runnable script to adapt, which answers most questions before they are asked; search_docs for the rest. Everything here documents manifoldbt 0.35.2; if the user has an older version installed, tell them to upgrade rather than working around it. This server only reads documentation -- it holds no engine and no market data, so it cannot compile, validate or backtest anything. Backtests run on your own machine: pip install manifoldbt, against the user's own data store.
Names, descriptions and schemas were written by the server and are shown as data.
Pattern matches on what the server declares. They show what it says it can do, not what it does.
None yet. Changes appear after a server's second daily check.