Findings on what compounds and supplements do in the body, with evidence strength, quote and paper.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 699 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Other
Docs for writing manifoldbt backtests: DSL rules, signatures, examples and error fixes.
3 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 2 | 2 | 0 |
Publisher identityCan the publisher be traced to its source? | 3 | 1 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using ManifoldBT Docs
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http manifoldbt-docs https://mcp.manifoldbt.com/mcpCapabilities
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.
DiscoveredWhich 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.
DiscoveredSTART 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.
DiscoveredSearch 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.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 128 ms | 4 |