Vibedonate MCP server
BitTorrent-style mesh for AI inference across agentic CLIs. Local-first.
0 stars27 downloads/wk
Reviews
Write oneNobody has reviewed Vibedonate yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Vibedonate tools (2)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
request_capacityPre-flight: ask whether this node can serve `tokens` for `peer`. Checks the donate:compute consent grant, peer authorization (allow-list/org/open), on-device compute availability, the idle window, local activity, and the daily cap. Returns a decision and a reason. Does not consume capacity.
statusReport the current vibedonate config, the resolved on-device model, metering totals (donated / donatedToday / received), and whether the node is sharing capacity right now.
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- Code scan9 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 10 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Vibedonate compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 95% of 48,255 servers
- Tools
- 2
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 27
- more than 14% of 12,191 servers with a package
What its tools let an agent do: 2 read
Install Vibedonate in Claude Code, Cursor or VS Code
Runs npx -y vibedonate on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add vibedonate -- npx -y vibedonate
What the publisher says
From the Vibedonate repository's README, as published. We do not edit it. Read it on GitHub
vibedonate
BitTorrent-style mesh for AI inference — donate spare local compute across Claude, Codex, Gemini, Grok, pi. Your hardware, opt-in, metered.
Part of the Vibe Suite — companion tools for agentic coding CLIs (Claude Code, Codex, Gemini, Grok/pi, Kimi). Ships as CLI + npm package + MCP server.
Local-first: runs on your own machine, no data out (consent model in @pooriaarab/vibe-core).
v0 = the local-compute tier only. This release donates spare compute from a model on your machine, metered against a daily token cap and scoped to an allow-list. Routing a stranger's inference through your logged-in subscription or API key is a different trust surface and needs trust/legal design first (see docs/spec.md §"Open questions"). It is deliberately not in v0.
Install
# use it
npx vibedonate share --compute --idle 22:00-07:00 --cap 2M --pool allowlist:alice,bob
# or install globally
npm install -g vibedonate
vibedonate statusAs a library:
npm install vibedonateQuick start (CLI)
# Arm donation: local compute, 22:00–07:00 UTC, 2M tokens/day, only alice & bob.
vibedonate share --compute --idle 22:00-07:00 --cap 2000000 --pool allowlist:alice,bobvibedonate — enabled · ● your machine · opt-in
tier: compute
idle: 22:00-07:00 (UTC)
cap: 2,000,000 tokens/day
pool: allowlist [alice, bob]
usage: donated 0 (today 0) · received 0 · 0 receipt(s)
sharing: yes (now 2026-07-26T03:17:55Z)vibedonate status # config + metering totals + whether sharing right now
vibedonate stop # disable (revokes the donate:compute consent grant)
vibedonate mcp # run the MCP server over stdio
vibedonate --version
vibedonate --helpState lives in $VIBEDONATE_DIR (default ~/.vibedonate): config.json, consent.json, metering.json. Nothing leaves your machine.
--pool
--cap
A bare integer (2000000) or shorthand (2M, 500k). Scoped to the UTC day of each receipt.
Quick start (library)
import {
createDonationConfig,
isSharingActive,
createMeteringLedger,
authorizePeer,
DONATE_COMPUTE_SCOPE,
resolveCompute, // cascade-backed on-device model resolution
evaluateCapacity, // the shared gate (MCP + mesh runtime)
createLocalMeshRuntime,// serves a request + commits a receipt
createDonationHooks, // lifecycle events into the suite notify channel
createConsentLedger, // from @pooriaarab/vibe-core, re-exported
} from 'vibedonate';
const config = createDonationConfig({
idle: '22:00-07:00', // wraps midnight
cap: '2M', // 2,000,000 tokens/day
pool: 'allowlist:alice,bob',
});
const now = new Date();
const ledger = createMeteringLedger(); // in-memory; pass a store to persist
const consent = createConsentLedger();
consent.grant(DONATE_COMPUTE_SCOPE); // arm donation
// The schedule boolean: enabled AND not busy AND under cap AND inside the window.
const active = isSharingActive(config, now, /* systemBusy */ false, ledger.totals(now).donatedToday);
// What "donate local compute" actually means: is there an on-device model to
// serve with? Resolved through vibe-core's cascade with egress forbidden, Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Vibedonate: common questions
- Is Vibedonate MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Vibedonate safety report
- How do I install Vibedonate?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Vibedonate need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Vibedonate maintained?
- The last commit was 50 days ago (2026-09-14). The latest release is v0.4.2.
- How does Vibedonate compare with other MCP servers?
- safety score 92/100 (higher than 95% of 48,255 servers); tools 2 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.