# Clawboo vs Vibe-Trading (slim)

> Vibe-Trading scores 62.8 (B) to Clawboo's 61.4 (C) for multi-agent orchestration. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/clawboo-vs-vibe-trading.md (~6,200 tokens) · this version ~2,930 tokens · JSON https://www.anchorterminal.com/compare/clawboo-vs-vibe-trading.json · canonical https://www.anchorterminal.com/compare/clawboo-vs-vibe-trading
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-01
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Vibe-Trading scores 62.8 (B) on agent readiness against Clawboo's 61.4 (C), and leads in 2 of 7 scored categories. Clawboo leads on schema & documentation, agent ergonomics and transparency & trust. Both do multi-agent orchestration.

- Clawboo: C 61.4, rank #555 of 1251 · https://www.anchorterminal.com/tools/clawboo.min.md
- Vibe-Trading: B 62.8, rank #491 of 1251 · https://www.anchorterminal.com/tools/vibe-trading.min.md
- Clawboo, good for One person on one computer who wants several coding and general agents on one board, with shared memory and a lead agent that routes work. Ahead on Schema & documentation, 83 against 72; Agent ergonomics, 75 against 67; Transparency & trust, 58 against 53.
- Vibe-Trading, good for A person or a pipeline that wants a ready-made finance research agent over free market data, with backtests, swarm reviews and exports, run on their own machine or used as an MCP server by another agent. Ahead on Reliability, 63 against 52; Maintenance & community, 82 against 51. Also Runs on your own machine.

| Category | Clawboo | Vibe-Trading |
| --- | --- | --- |
| Reliability (16%) | 52 | 63 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 72 |
| Agent ergonomics (13%) | 75 | 67 |
| Security & auth (14%) | 70 | 70 |
| Payments & pricing (10%) | 60 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 51 | 82 |
| Transparency & trust (7%) | 58 | 53 |

| Fact (where they differ) | Clawboo | Vibe-Trading |
| --- | --- | --- |
| Vendor | Sanreds | HKUDS |
| Transports |  | stdio, Streamable HTTP, SSE (legacy) |
| Tools exposed | none | 82 |
| llms.txt | yes | no |
| Popularity | 100 npm/wk | 37k stars |

Why the edge:
- Maintenance & community, Vibe-Trading +31: Clawboo 51 (0.5.0 was published to npm on 21 October 2026 (30). Two releases in the 90 days to 1 November 2026, 0.4.0 on 28 September and 0.5.0, below the three the line asks for (0). github.com was unreachable, so replies to issues, pull requests and Discussions are unchecked. The CI file cites issue #140 as fixed (3). One public npm package, current, with no entry in the official MCP registry for its four servers (10). CI, CodeQL, weekly Dependabot and SLSA provenance on 0.4.0 and 0.5.0, with `@composio/client` pinned to an alpha (8).); Vibe-Trading 82 (v0.1.18 was published to PyPI on 21 October 2026, four days before this check (30). Six releases in the 90 days to 25 October, 0.1.13 to 0.1.18 (20). 761 commits and 253 merge commits in the last 30 days from more than ten authors, against 7 open issues and 57 open pull requests on the repository page. Issue and pull request threads weren't read, a judgement call (18 of 25). An MCP server that isn't in the official MCP registry (searches for vibe-trading and hkuds on 25 October 2026 found nothing). It is published on PyPI, as a Docker setup and on ClawHub (5 of 15). Hash-locked requirements checked in CI on three operating systems, Dependabot set to monthly, and dependency floors raised for named CVEs, such as `mcp>=1.30.0` for CVE-2026-59951 (9 of 10).)
- Reliability, Vibe-Trading +11: Clawboo 52 (Read as local software. The official npm package `clawboo` states Node.js 22.12 or newer, and the README says macOS, Linux and Windows are supported (20). `ci.yml` runs lint, typecheck, Vitest and a real-concurrency suite on Linux and platform suites on Windows and macOS, and `publish.yml` reruns build, lint, typecheck, tests and a clean-install boot before it publishes. 0.5.0 carries provenance from that workflow on main, so its checks passed at that commit, but run results on main couldn't be read (15). github.com was unreachable, so open crash and regression issues are unchecked. A known-issues page lists 25 entries with a status each, three of them fixed on main (5). Changesets write a changelog entry per release, and removals and the 0.2.0 database reset are called out, though breaking changes arrive in minor versions before 1.0 (12). Version 0.5.0, and SECURITY.md says pre-1.0 (0).); Vibe-Trading 63 (Read with the local-software lines, as for nanobot and Agent Zero, since the owner runs it. `vibe-trading-ai` installs from PyPI for Python 3.11 or newer, with classifiers for 3.11 to 3.13, and a Docker Compose setup ships in the repository (20). A CI workflow runs the test suite on pushes and pull requests to main, with hash-locked dependency checks on Linux, macOS and Windows, and the repository holds 961 test files. Whether the latest runs on main passed couldn't be read, because GitHub's Actions pages weren't reachable (15 of 25). The repository page showed 7 open issues and 57 open pull requests on 25 October 2026 against 761 commits in the 30 days before, and the 0.1.18 notes list two known issues already fixed on main. Issue threads weren't read (18 of 25). CHANGELOG.md says it follows Semantic Versioning, with dated entries from 0.1.8, a Known issues section and an upgrade note for the LangChain 1.x move in 0.1.10, but on 0.x breaking changes ride in minor versions and there is no Breaking section (10 of 15). Version 0.1.18 with the classifier Development Status 4, Beta (0).)
- Schema & documentation, Clawboo +11: Clawboo 83 (Harness reading of the framework line, as for Paperclip. The REST API's 199 routes are documented per resource with parameters, bodies and responses, and the MCP tools reference gives typed arguments for every tool on the four servers, but no OpenAPI file was found (17). llms.txt, llms-full.txt and a Markdown copy of every page at `.md` on docs.claw.boo (10). The docs say what each part does and does not cover, with known issues, production defaults and a limits page that names the code line behind each number (17). Tool arguments are typed with required and optional fields and documented caps, such as 24 live subtasks per parent and limits lowered to 1,000, with free-text task bodies (12). curl examples on each API page, an events and errors reference, and the exact error strings each MCP tool returns (14). A dated changelog for every release with an Unreleased section, though API paths carry no version and every MCP server reports 0.1.0 (13).); Vibe-Trading 72 (Harness reading of the lines, as for nanobot. The MCP server's tools take typed JSON Schema inputs generated from Python signatures through FastMCP, with a string output schema, and the API server serves FastAPI's OpenAPI file locally (keyless on loopback, behind the key otherwise). No published OpenAPI file or tool manifest outside the running program (20 of 25). No llms.txt on vibetrading.wiki, where /llms.txt redirects to the home page, and the docs are drawn by script from `content.en.js`. The repository carries Markdown READMEs in seven languages and an agent skill file, `agent/SKILL.md` (5 of 10). Tool descriptions say what each does, its arguments and what to call first, such as `list_skills()` before `load_skill`. The server's own header says every tool is read-only apart from `refresh_strategy_evidence`, while `write_file` is also exposed (14 of 20). Inputs are typed, but many choices are free strings (`protocol`, `risk_tier`, `format`) and several take free dictionaries (8 of 15). Many worked examples in the README and a troubleshooting page that names failure states such as `no_progress` and the 403 from another device; tool errors come back as JSON with an `error_type` (12 of 15). Dated CHANGELOG.md, GitHub release tags and versioned docs, though the docs still name 0.1.16 as latest (13 of 15).)
- Agent ergonomics, Clawboo +8: Clawboo 75 (Harness reading, scored on what an agent or pipeline driving it has to supply. Four MCP servers keep tool lists small (12 Tasks tools, 4 Memory tools, 2 or 3 TeamChat tools, and Tools with four demonstration builtins plus granted connectors), Clawboo Native gets a read-only Tasks subset, and Tools results over 16 KiB are trimmed with a handle to read the rest (22). Circuit breakers stop task-runner runs after more than 30 tool calls or 200,000 tokens a minute, and team chat caps hand-offs at 8 a turn and three levels. Budgets warn only unless set to a hard cap, and a hard cap stops most runs only between runs (14). REST errors use one `{error}` shape, refused MCP calls return `denied:` with a reason prefix, and 429s carry `Retry-After` (16). `claim_task` and `assign_task` are atomic, illegal status changes are refused by name, the board survives restarts and routines resume after failure. No MCP tool annotations are documented (14). One `npx` command and a provider key or a local Ollama, but Claude Code teammates need a global install with the Agent SDK, and there is no client SDK (9).); Vibe-Trading 67 (Harness reading, scored on what an agent or script driving it has to supply. The MCP server registers 82 tools, with about 44,300 characters of descriptions across the 71 defined in the server file, and no toolsets or read-only subset (5). Since 0.1.18 the built-in agent loads tool schemas on demand, and skills load by section and offset, which keeps its own context smaller (plus 7, 12 of 25). Rows are capped by default, `read_run_artifact` pages by offset, row count and columns, oversized results are written to the run directory, the agent stops after eight tool iterations without a new result, and goals take token, turn and time budgets (18 of 20). JSON error envelopes with a type, a `--json` mode for `vibe-trading run` and a troubleshooting page, with no documented exit codes (15 of 20). No readOnlyHint or destructiveHint annotations on MCP tools. An identical call is refused from its second failure, failed swarm runs resume with completed tasks kept, interrupted web replies are checkpointed and TAP-routed Alpaca orders carry a deterministic `client_order_id` (12 of 20). `pip install` and `vibe-trading init` start it, market data works with no key, and a model key, Ollama or an existing Codex, Copilot or Claude Code login is required. Python only, with a REST API and no SDK in a second language (10 of 15).)
- Transparency & trust, Clawboo +5: Clawboo 58 (MIT, Copyright 2026 Sanreds, with a third-party notices file (30). The docs list every file Clawboo writes, which copies of keys are encrypted and which are plain text, retention for stored tool results (7 days) and pending approvals (24 hours), and that prompts go only to connected providers. There is no privacy statement, and the website wasn't read (22). The 0.1.x line is deprecated on npm with a note in the changelog, and removals are dated in release notes, with no written deprecation policy or notice period (10). No telemetry, with the server's own outbound requests disclosed, though the npm update check has no setting (18).); Vibe-Trading 53 (MIT (30). There is no hosted service, so no privacy policy is needed. The README says where data lives (named Docker volumes or `~/.vibe-trading/`), that broker keys go to the OS keyring and that generated code doesn't receive model or broker secrets. Nothing was found stating what reaches the model provider or the search fallbacks (15 of 30). Dated changelog entries, a Known issues section, an upgrade note for 0.1.10 and dated retirements such as `mootdx` leaving the default chain in October 2026. No deprecation policy or notice period (9 of 20). No telemetry was found in the source, but the docs do not state that nothing is collected (13 of 20).)