MCP server: persistent, self-revising hypothesis-DAG for agentic R&D
MCP server: persistent, self-revising hypothesis-DAG for agentic R&D
A persistent, self-revising hypothesis DAG for agentic R&D — exposed as an MCP server.
create_hypotheses — Create one or many nodes with parent_ids, exclusion_group, is_goalget_next_targets — Thompson Sampling — returns the next hypothesis to test, under a leaserecord_evidence — Record experiment results; triggers write-back propagationgenerate_learning_path — What we learned, in order, and what it cost — separates conclusions an experiment paid for from ones the engine inferred freeget_workspace_info — Which belief state you are connected to and which layer chose it — start here when the graph is unexpectedly emptyupdate_status — Manually set node status (rarely needed — the engine does it)get_dag_context — Get a subgraph view for the agent's context windowrender_dag_map — Mermaid.js diagram of the current belief stateget_goal_status — Check whether the goal node is metget_conflicts — List unresolved conflicts (integration failures)suggest_discriminating_experiment — For a conflict, suggest the swap that separates the culpritslist_nodes — List/filter nodes by status, depth, or exclusion groupget_evidence_history — Full evidence trail for a nodeget_active_claims — List nodes with active leasesCompare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| get_workspace_info | Which belief state you are connected to and which layer chose it — start here when the graph is unexpectedly empty |
| update_status | Manually set node status (rarely needed — the engine does it) |
| get_dag_context | Get a subgraph view for the agent's context window |
| render_dag_map | Mermaid.js diagram of the current belief state |
| get_conflicts | List unresolved conflicts (integration failures) |
| suggest_discriminating_experiment | For a conflict, suggest the swap that separates the culprits |
| what_would_change_my_mind | Name the cheapest experiments that would overturn a goal's current conclusion, weakest evidence first |
| list_nodes | List/filter nodes by status, depth, or exclusion group |
| get_evidence_history | Full evidence trail for a node |
| get_active_claims | List nodes with active leases |
| renew_claim | Extend a lease on a node |
| release_claims | Release one or all leases |
| invalidate_upstream | Revert VERIFIED status from parents based on child failures |
| verify_upstream | Propagate confirmation up the dependency chain |
{
"mcpServers": {
"hypotree": {
"command": "uvx",
"args": [
"hypotree"
],
"env": {
"HYPOTREE_WORKSPACE_ID": "my-project"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| HYPOTREE_WORKSPACE_ID | Declared in the maintainer’s client configuration. | Check documentation |
Inspect PostgreSQL schemas and run read-only queries with the archived MCP reference server. Review its maintenance status before choosing it.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Use the Supabase MCP server to inspect database schemas, query project data and retrieve docs through a project-scoped connection.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.