# ManifoldBT Docs

> Docs for writing manifoldbt backtests: DSL rules, signatures, examples and error fixes.

- name: com.manifoldbt/docs
- version: 0.8.0
- connection class: R0 (autonomous)
- trust: 83/100 flags: no-repository
- quality: 80/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.manifoldbt%2Fdocs
- tools: https://api.protogrid.dev/v1/servers/com.manifoldbt%2Fdocs/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "docs": {
      "type": "http",
      "url": "https://mcp.manifoldbt.com/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% +updated-7d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 80/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 75 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: search_docs (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); explain_error (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_capabilities (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 544 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump
- pass `tools.hidden_text`: no hidden text in tool names, descriptions, schemas or annotations

### stability: 100 (weight 15)

- pass `stability.changes`: 1 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name
- pass `stability.new_links`: no tool change named a new site

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 4, about 544 tokens to load them all
- tool set hash: 0a3fd0c0e7c46880f4692ef1f36f0055
- tools last changed: 2026-11-08T18:41:20.432Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.manifoldbt/docs.svg)](https://protogrid.dev/servers/com.manifoldbt/docs)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-11-08 `search_docs` changed (description)
  - before: 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').
  - after: 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.

Full history: https://api.protogrid.dev/v1/servers/com.manifoldbt%2Fdocs/changes

## Remotes

- https://mcp.manifoldbt.com/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (4)

- `explain_error`: 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.
- `get_capabilities`: 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.
- `list_topics`: 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 and cross-asset 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.
- `search_docs`: 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.