Vibedate

Name: Vibedate
Author: pooriaarab

by pooriaarabversion 0.8.8i★ –iRuns on your computer

Registry nameio.github.pooriaarab/vibedate

Install

Overview

Description from the maker (original English)

Dating by tokens, matched by usage league 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": {
    "vibedate": {
      "command": "npx",
      "args": [
        "-y",
        "vibedate",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add vibedate -- npx -y vibedate mcp

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "vibedate": {
      "command": "npx",
      "args": [
        "-y",
        "vibedate",
        "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": {
    "vibedate": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "vibedate",
        "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 32688 servers in this category
Published to the registry more recently than 20% of the other 32688 servers in this category
Basic checks equal to or better than 100% of the other 32688 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 Vibedate 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.8.8) 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, 御府和田玉在售作品查询

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

御府和田玉在售作品查询

by 163yu.com

Live in-stock Hetian jade from Yufu, Shanghai: prices, monthly price guide, book a viewing.

Runs in the cloudUpdated 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.

vibedating

npm package · Install · Quick start · Privacy · Alternatives

Dating by tokens — connect your Claude Code / Codex usage, get sorted into a league (1M / 5M / 10M / 100M / 1B+), and match with people who burn tokens the way you do. The premise: heavy users of these tools share something worth matching on.

Part of the Vibe Suite — companion tools for agentic coding CLIs. Ships as CLI + npm package + MCP server, plus a local web app. Built on @pooriaarab/vibe-core.

Demo

▶ Watch the launch video — she matched with the man of her dreams. He was coding in a basement.

https://github.com/pooriaarab/vibedating/raw/main/branding/launch-video.mp4

Local-first. Raw token usage is read and stored on your own machine and

never leaves it. Only the coarse league *bucket* is ever shared — never the

raw number, never per-project breakdowns. Live matching is peer-to-peer over a

DHT (no central server) and opt-in only; without it the pool is a local

seeded demo.

Status

v0 — works locally, privacy-first. Usage is verified from your harness's real local logs via vibe-core's readHarnessUsage (source real → verified: true); when no logs are readable you can self-report (VIBEDATING_TOKENS, unverified) or fall back to a demo value (unverified). Handles are bound to a persistent ed25519 identity (~/.vibedating/identity.json, mode 0600): every hello is signed, and a forged signature gets the peer dropped.

Install

npm install -g vibedate

…or run it ad-hoc:

npx vibedate connect

Quick start

# 1. Read your usage, compute + print your league (stored locally at ~/.vibedating)

vibedating connect

2. See candidates in your league (same or adjacent tier)

vibedating matches

3. (Opt-in) find live same-league peers over the DHT — no server

vibedating discover --live # shares ONLY handle+league+harness+verified flag+identity pubkey

4. Open the local web app in your browser (served from your machine)

vibedating open

Self-report a token count (otherwise a demo value is used):

VIBEDATING_TOKENS=23400000 vibedating connect   # also accepts 12M / 1.2B / 500k

All commands

vibedating connect            Read usage, compute + print your league

(first run auto-assigns a memetic handle — never @you) vibedating matches [--live] List candidates in your league (live peers if any, with last-message time) vibedating discover [--live] Find live same-league peers over the DHT (opt-in) vibedating live [--keep-alive] Live text chat (--keep-alive / non-TTY survives stdin EOF) vibedating handle [@name] Print or set your handle vibedating daemon [start|stop|status|install|uninstall] Notify-only background daemon — alerts on NEW matches, never opens chat/video; install = run on login (launchd/systemd) vibedating open [--port N] Serve the local web app (default: random free port) vibedating mcp Run the stdio MCP server (tools: profile, matches) vibedating --version vibedating --help

Live P2P discovery (opt-in)

vibedating discover --live joins the public hyperswarm DHT on your league topic — sha256('vibedate:' + leagueBucket) — so same-league peers find each other with no central server. On each encrypted connection the two sides exchange a one-line hello with only { handle, league, harness, verified, pubkey, nonce, sig } — the proof fields sign the hello with your persistent ed25519 identity so a handle can't be impersonated; raw usage is never put on the wire. Discovered peers are stored in ~/.vibedating/peers.json and shown by vibedating matches.

Live discovery is off by default. The --live flag is the explicit opt-in (persisted as the share:live consent scope); every live run prints what it shares before joining. Ctrl+C leaves the swarm cleanly.

Three faces, one local engine

The same local engine drives all three, so you can use it wherever you work:

Web — vibedating open serves the dating UI (profile, match stack, league ladder) at http://localhost:PORT. The page reads your league + matches from a tiny local JSON endpoint.
CLI — vibedating connect / matches.
MCP — vibedating mcp exposes profile (your league) and matches to any MCP host (Claude Code, Codex, Cursor, …).

As a library

import { league, matches, readUsage, CANDIDATES } from 'vibedate';

const usage = await readUsage('claude-code'); // { totalTokens, verified, ... } const lg = league(usage.totalTokens); // { name: '10M', min: 10_000_000 } const who = matches(lg.name, CANDIDATES); // same/adjacent-tier candidates

Privacy

Raw usage stays local. totalTokens is read into memory, stored at ~/.vibedating/state.json, and shown in the web app only behind an opt-in toggle. It is never transmitted.
Only the league bucket is shared — with the local demo pool, and (only if you opt in with --live) as { handle, league, harness, verified, pubkey, nonce, sig } with same-league peers over the hyperswarm DHT. The handshake parser whitelists those fields, so a peer can't even be *sent* anything else into your process; the verified flag and identity pubkey are the only additions, never a token count.
Consent for sharing the league is modeled with @pooriaarab/vibe-core's consent ledger (scope share:league), granted on connect and revocable on reset. Live P2P discovery has its own scope (share:live), default off.

Leagues & matching

Bucketed by lifetime tokens; you match within your league or an adjacent tier (so the tiny 1B+ pool still has people to match with):

League	Tokens (lifetime)
1M	1M – 4.99M
5M	5M – 9.99M
10M	10M – 99.9M
100M	100M – 999M
1B+	1B+

Prototype

An interactive, self-contained UX prototype (no build, no network): docs/prototype.html. The shipped local web app (vibedating open) is an adapted, data-driven version of this prototype.

Alternatives

Mainstream dating apps (Hinge, Bumble, Tinder) match on photos and prompts; vibedating matches on a signal that is hard to fake: how much compute you actually burn.
Speed-networking and community tools (Discord servers, hackathons) find other builders; this finds builders whose usage league sits near yours.

License

MIT

Vibedate

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

御府和田玉 在售作品查询

README from the maker

vibedating

Demo

Status

Install

Quick start

2. See candidates in your league (same or adjacent tier)

3. (Opt-in) find live same-league peers over the DHT — no server

4. Open the local web app in your browser (served from your machine)

All commands

Live P2P discovery (opt-in)

Three faces, one local engine

As a library

Privacy

Leagues & matching

Prototype

Alternatives

License

御府和田玉在售作品查询