Vibedonate

Name: Vibedonate
Author: pooriaarab

by pooriaarabversion 0.4.2i★ –iRuns on your computer

Registry nameio.github.pooriaarab/vibedonate

Install

Overview

Description from the maker (original English)

BitTorrent-style mesh for AI inference across agentic CLIs. Local-first.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "vibedonate": {
      "command": "npx",
      "args": [
        "-y",
        "vibedonate",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add vibedonate -- npx -y vibedonate mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "vibedonate": {
      "command": "npx",
      "args": [
        "-y",
        "vibedonate",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "vibedonate": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "vibedonate",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account pooriaarab, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 18336 servers in this category
Published to the registry more recently than 18% of the other 18336 servers in this category
Basic checks equal to or better than 100% of the other 18336 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Vibedonate safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.4.2) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, NexusWindows

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

NexusWindows

by pironjulien

Windows computer use in the background: desktop apps driven without your mouse or keyboard.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

vibedonate

Package · Setup · Runtime surfaces · Compare

vibedonate is an open-source, self-hosted compute-sharing experiment for developers who use coding agents. Your hardware, opt-in, metered. It provides peer transport, donation controls, and local ledgers in the Vibe Suite. The current CLI mesh runs an echo stub; its separate Ollama runner is not connected to mesh jobs.

Install

npm install -g vibedonate

Requires Node.js 18 or later. Includes TypeScript declarations and three direct runtime dependencies.

Run your first local check

vibedonate status

On a fresh installation, the output reports that the node is not armed. No credentials or environment variables are required. No sharing starts from this command. The CLI reads exported environment variables; it does not load .env files.

For an opt-in transport demo, run this donor in one terminal:

vibedonate share --compute --idle 00:00-23:59 --cap 2M --pool allowlist:consumer --handle donor

Run the consumer in another terminal:

vibedonate request "hello" --pool allowlist:consumer --handle consumer

With reachable peers inside the UTC window, the consumer prints olleh. This is the echo stub, not AI inference. Stop the donor with Ctrl+C, then run vibedonate stop to revoke persisted consent.

How it works

share -> saved config + consent -> Hyperswarm pool discovery

| consumer prompt -> donor checks -> echo stub -> result + metering receipt

status / MCP preflight -> separate Ollama availability check payment flags -> stub wallet + local payment ledger

Announcements contain handle, pool, compute tier, and optional payment terms. Prompts and results cross connected peer links. Raw usage totals are not announced. Local files default to ~/.vibedonate.

Why it exists

vibedonate explores opt-in donation controls around spare local compute. Petals distributes model execution; Ray Serve provides model-serving infrastructure. This package focuses on consent, schedules, recipient pools, and metering, with experimental peer transport.

Compare

Checked 2026-10-14 against the Petals research paper and Ray Serve documentation.

Property	vibedonate	Petals	Ray Serve
Scope	Donation controls and echo mesh demo	Collaborative model inference and fine-tuning	Distributed model serving
Execution	Default mesh uses echo stub	Distributed model blocks	Deployed model-serving applications
Interface	Node.js library, CLI, agent preflight	Model inference interface	Python deployment and inference APIs

Coverage

Integration or tier	Status	Source behavior
Hyperswarm	Implemented	Same-pool peer discovery and request/result transport
Ollama	Separate runner	Detects executable; invokes `ollama run`; not wired to mesh CLI
Echo mesh model	Stub	Reverses prompts; records 100 tokens per default job
USDC / x402-style payments	Stub	Deterministic wallet proofs and local ledger; no settlement
Base	Scaffold	Accepted payment chain label
Ethereum	Scaffold	Accepted payment chain label
Polygon	Scaffold	Accepted payment chain label
Subscription sharing	—	No shipped tier
API-credit routing	—	No shipped tier

There is one default chat runner, one default echo mesh model, and two MCP tools. Source inspection and local tests support these distinctions. No credentials, on-chain transactions, or public-network service guarantees were verified.

Common use cases

Node.js developers: test consent and capacity decisions through the exported library.
Hyperswarm experimenters: exchange echo jobs between same-pool peers.
Ollama users: inspect local chat-runner availability before building a custom integration.
Agent builders: call MCP request_capacity to check a proposed donation without executing a job.
Vibe Suite users: inspect hash-chained usage and payment records on their own machine.

Features

Consent: share grants donate:compute; stop revokes it in persisted storage.
Schedules: UTC idle windows and configurable daily token caps.
Recipient pools: open, org: , , and allowlist: .
Metering: local hash-chained receipts with a chain verification method.
Payments: optional price metadata and stub payment records; free jobs by default.
Suite hooks: exported donation lifecycle hooks use vibe-core events and notifications.

Runtime surfaces

The Node.js package exports configuration parsers, consent helpers, capacity evaluation, metering, payment stubs, and compute resolution.

vibedonate share --compute --idle HH:MM-HH:MM --cap 2M --pool open

[--handle name] [--price 0.001] [--chain base|ethereum|polygon] vibedonate request "prompt" --pool open [--handle name] [--timeout milliseconds] [--pay 0.001] vibedonate status vibedonate stop vibedonate wallet vibedonate mcp vibedonate --help / -h vibedonate --version / -v

vibedonate mcp starts a stdio Model Context Protocol (MCP) server with exactly two tools:

Tool	Behavior
`status`	Config, consent, compute availability, schedule state, and totals
`request_capacity`	Preflight `{ peer, tokens }`; returns an allow/deny decision without inference or a receipt

Delivery and behavior limits

The CLI donor defaults to createEchoModel(). Installing Ollama does not replace it with model inference. The separate local runtime records capacity receipts; it does not execute a prompt. The CLI uses stubWallet(). Payment success means a synthetic proof passed, not that USDC moved on Base, Ethereum, or Polygon. Peer authorization compares announced handles. It does not authenticate organization membership or bind handles to trusted identities. CLI activity checks default to “not busy”; no automatic machine-idle detector is wired into the donor. The running donor holds its initial config and consent objects. Use Ctrl+C to stop it; a separate stop process does not close it. The mesh checks whether today's total is below the cap before a job; a job can exceed the remaining allowance. The capacity preflight has a stricter request-fits check. Do not assume both paths enforce identical bounds. Discovery defaults to 15 seconds; each attempted donor gets up to six seconds. Total elapsed time can exceed the discovery timeout. Hash chains detect inconsistent record content; they do not prevent someone from rewriting the whole local ledger.

Integration guides

Ollama runner: install Ollama and pull qwen2.5:7b; set VIBEDONATE_OLLAMA_MODEL to choose another installed model.
Separate state: export VIBEDONATE_DIR to override ~/.vibedonate.
Demo pool (not access control): use the same allowlist:consumer string on both peers and --handle consumer for requests. Any peer that announces a matching handle passes the check.
Organization pool: include explicit members, such as org:team,alice; org:team alone authorizes no members.
Agent setup: configure your MCP host to launch vibedonate mcp over stdio.

Status

Version 0.4.3 is experimental and pre-1.0. Public case studies are not yet published. No public documentation site is configured; the operational guidance is self-contained here. Use GitHub issues for support; repository access may be required. For contributions, run npm ci, npm run typecheck, npm run build, and npm test.

FAQ

Which integrations are verified?

vibedonate has source-backed peer transport and a separate Ollama runner. Local tests do not certify public peers or blockchain settlement.

Does vibedonate provide a managed inference service?

vibedonate runs on your hardware. It provides no managed inference pool, availability guarantee, or hosted account service.

Does the CLI run Ollama for donated jobs?

vibedonate uses an echo stub for default CLI mesh jobs. The Ollama chat runner exists as a separate library path.

How is vibedonate different from Petals?

vibedonate experiments with donation controls and a request/result mesh. Petals distributes model execution across participants.

How is vibedonate different from Ray Serve?

vibedonate supplies local donation controls and a CLI experiment. Ray Serve supplies infrastructure for deployed model-serving applications.

Can I earn real USDC with vibedonate?

vibedonate ships a stub wallet and local payment records. The CLI does not submit or verify real blockchain payments.

Does stop terminate an active donor?

vibedonate stop changes persisted config and consent. Stop the active donor process with Ctrl+C to leave the mesh.

Does vibedonate share subscription quotas or API credits?

vibedonate ships only the compute tier. Subscription and API-credit routing are not implemented.

License

MIT.

Vibedonate

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

NexusWindows

README from the maker

vibedonate

Install

Run your first local check

How it works

Why it exists

Compare

Coverage

Common use cases

Features

Runtime surfaces

Delivery and behavior limits

Integration guides

Status

FAQ

Which integrations are verified?

Does vibedonate provide a managed inference service?

Does the CLI run Ollama for donated jobs?

How is vibedonate different from Petals?

How is vibedonate different from Ray Serve?

Can I earn real USDC with vibedonate?

Does stop terminate an active donor?

Does vibedonate share subscription quotas or API credits?

License