rea
Reverse engineer anything with agents, from app behavior down to native binaries.
Drive terminal coding agents by voice, with receipts that never claim more than they proved.
Skills that teach the AI this kind of work; they work alongside this one
Reverse engineer anything with agents, from app behavior down to native binaries.
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 11/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 7/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 18/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Yapitalism. Follow https://mcp.popnx.com/i/aytuncyildizli-yapitalism.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Yapitalism for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "yapitalism": { "command": "uvx", "args": [ "yapitalism", "--stdio", "your-value" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Yapitalism tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
SettingsDeveloperEdit Config
{
"mcpServers": {
"yapitalism": {
"command": "uvx",
"args": [
"yapitalism",
"--stdio",
"your-value"
]
}
}
}Use Yapitalism and tell me what you can do for me, then show me one thing✓ If Claude says it is using Yapitalism or shows a Yapitalism tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Yapitalism yet
Yapitalism runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Yapitalism
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Yapitalism for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user yapitalism -- uvx yapitalism --stdio your-value 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Yapitalism tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user yapitalism -- uvx yapitalism --stdio your-valueYou should see Yapitalism listed as connected
Use Yapitalism and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Yapitalism or shows a Yapitalism tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Python (uv) on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Yapitalism for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "yapitalism": { "command": "uvx", "args": [ "yapitalism", "--stdio", "your-value" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Yapitalism tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
~/.cursor/mcp.json
Paste these settings, fill in the empty values and save
{
"mcpServers": {
"yapitalism": {
"command": "uvx",
"args": [
"yapitalism",
"--stdio",
"your-value"
]
}
}
}Use Yapitalism and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Yapitalism or shows a Yapitalism tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Python (uv) on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Yapitalism for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "yapitalism": { "type": "stdio", "command": "uvx", "args": [ "yapitalism", "--stdio", "your-value" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Yapitalism tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
MCP: Open User Configuration
Paste these settings, fill in the empty values and save
{
"servers": {
"yapitalism": {
"type": "stdio",
"command": "uvx",
"args": [
"yapitalism",
"--stdio",
"your-value"
]
}
}
}Use Yapitalism and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Yapitalism or shows a Yapitalism tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add --scope user yapitalism -- uvx yapitalism --stdio your-valueClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"yapitalism": {
"command": "uvx",
"args": [
"yapitalism",
"--stdio",
"your-value"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"yapitalism": {
"command": "uvx",
"args": [
"yapitalism",
"--stdio",
"your-value"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"yapitalism": {
"type": "stdio",
"command": "uvx",
"args": [
"yapitalism",
"--stdio",
"your-value"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
pypi: yapitalismBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
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 19, 2026
The registry name was verified with the GitHub account AytuncYildizli, which owns the repo
Code last changed 34 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for yapitalism@0.6.0
Checks only this package version, not every dependency · checked Nov 15, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/aytuncyildizli-yapitalism)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed 34 days ago, and the latest version (0.6.0) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP servers
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one Yapitalism | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
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.
Drive terminal coding agents by voice, and never let the answer claim more than it proved.
You are away from your desk. You speak; an agent in a terminal does the work; you get a spoken reply. That reply is the only thing you have — you cannot see the screen. So the worst failure is not a crash, it is the voice saying *"done"* while your text sits unread in a prompt box.
Yapitalism is a local MCP server that lets a voice client reach your coding agents, plus a receipt layer that decides what the voice is allowed to say. If you are at your desk, use your screen — this exists for the hours you are not.
Public pre-alpha. Local-only. No production deployment, no external messaging, and no automation
of closed-source clients.
MCP client (Codex · Hermes · Claude Code · Claude Desktop · Cursor)
│ MCP over loopback — no public endpoint, no OAuth, no relay ▼ yapitalism MCP server panes_list · pane_read · pane_send │ pane_await · pane_task │ panes_name · panes_unname │ panes_create · panes_resume · pane_clear ├── superset backend local host-service over tRPC (127.0.0.1:48900) └── tmux backend capture-pane / send-keys
The agents it addresses: codex, claude, kimi, opencode — recognised by measurement (a process tree on tmux, the host's own agent registry on Superset), never by a caller's claim. A pane running anything else is refused, because typing into a shell and pressing Enter is running a command.
The voice client never reaches your machine directly: it drives a local agent session, and that session talks to this server over 127.0.0.1. Nothing is exposed to the network.
pane_send returns a verdict, not a shrug.
| meaning | |
|---|---|
| GREEN | the agent echoed a one-time marker. It demonstrably received and processed the text — which is not a claim the work it then did is correct; no receipt can promise that, and this one does not try. |
| YELLOW | the write landed; processing was not proven. Never round this up. |
| RED | the backend refused the write. Nothing reached the terminal. |
YELLOW is the whole point. Text left unsubmitted in an agent's input box looks identical to work in progress from outside — same spinner, same scrolling output, same HTTP 200. A voice that rounds that up to "done" costs you hours before you notice.
Explicitly not acceptance: an HTTP 2xx, a PTY write returning, terminal output changing, a revision advancing, or the prompt echoing your own words back.
A fixed deadline reports on the clock, not on the agent. An agent that thinks for a minute and then answers correctly was verified all along, and calling that YELLOW teaches an operator to ignore YELLOW. So the wait is an idle timeout: it restarts whenever the pane changes, bounded by a hard ceiling.
Pane movement decides only whether to keep waiting. It is never evidence of acceptance — that stays the canary alone. A YELLOW therefore says which kind it is:
canary_timeout_pane_moving — the pane's text was still changing. Named after what was measured: a spinner, a clock, a log tail or a second agent sharing the pane all produce this without the intended agent doing anything. It is a hint that looking again may be worth it, never a claim that the agent is working.canary_timeout_pane_still — nothing moved at all.What remains irreducible: if an agent silently ignores the text and prints nothing, no mechanism here can distinguish that from an agent that never received it. Verification needs the agent to emit something.
Delivery is table stakes; the expensive failure is an agent that has been sitting on a yes/no question for forty minutes while you thought it was working. pane_await watches a pane until the agent's turn ends and says how; pane_task is send-then-await in one call — instruct, walk away, come back to one of:
| turn | meaning |
|---|---|
ended | prompt idle, screen stopped changing. The turn is over — spoken with "not that the work is correct" attached, never as "done". |
waiting_input | a blocking dialog owns the screen (trust / login / confirmation). You are the blocker, and the payload's tail carries the question so it can be quoted. |
agent_error | a known failure line owns the screen — Please run /login, a 401, a rate limit — named, not timed out. |
exited | the pane no longer runs an agent. |
running | still changing when time ran out. Unproven; offers to look. |
An ended verdict re-verifies the agent process is still alive before it is claimed: the frozen prompt of a dead pane must not be celebrated as a finished turn.
The bearer token answers *who is calling*; it never answered *what they may do*. Since 0.5.0: stdio clients write, always — the OS made that trust decision when it let the client spawn the process. Writes over HTTP are off by default and every refusal names the fix: yapitalism authority allow-http-writes, once, on that machine (yapitalism setup asks the same question while printing the HTTP registration lines). Reading, watching and doctor work on every transport regardless, and yapitalism-mcp --read-only turns writes off everywhere — install the watcher first, allow writes when it has earned them. Every write result carries its origin.
On tmux, the send path also pins the identity of the admitted agent (pid + start time) and re-verifies it immediately before Enter. An agent that exits into a shell between typing and submit gets the text staged but never submitted — typing is recoverable, Enter into a shell is command execution.
Most of the time this does not change what you do, and it is not read out loud. It is in the payload and in yapitalism setup, for when something goes wrong and you want to know what was actually checked before the write.
| meaning | |
|---|---|
host | the host refuses the write itself — the check and the write are one operation |
client | this process checks, then writes; real against what it covers, not atomic |
none | nothing checks |
{ "status": "GREEN",
"client_guarantees": ["idempotent_dispatch", "empty_prompt_check"], "missing_guarantees": ["optimistic_revision"] }
yapitalism setup prints the table for your machine. Today both backends land in client for most of it: the checks happen here, a moment before the write, rather than inside the host atomically with it. tmux cannot do the revision check at all.
No shipped Superset enforces these itself, and this tool used to claim it did. It concluded "guarded" from the fact that a procedure named terminal.send was routed. The terminal.send Superset actually ships takes {terminalId, workspaceId, text, submit} and guards nothing. The levels are now read from what the host's own validator *requires* — the difference between a name and a contract.
Both backends reach GREEN, and GREEN means the same thing either way: the agent emitted the one-time marker, so it received the text and processed it. The table is for diagnosing a machine, not something to reason about on every send.
Whether you are a person or someone's agent asked "should I install this," the claims worth checking and where each one lives — verify, do not take our word:
src/yapitalism/mcp/tmux.py and src/yapitalism/mcp/backends/, each guard with a test named after the failure it prevents.tests/test_canary.py for why an echo cannot satisfy it.A peer is another machine's yapitalism server, mounted under its own namespace: the codex pane tmux:%0 on the machine studio is studio:tmux:%0 here, in the same panes_list, addressable by the same pane_send. Receipts pass through verbatim — the peer proved them next to its own terminals, and this side only gives the ids their machine name back.
# on the peer (reachable over your tailnet):
YAPITALISM_MCP_HOST=100.x.y.z yapitalism-mcp # tailnet bind requires the bearer gate
yapitalism peers add studio http://100.x.y.z:8792/mcp --token-file
peers add verifies the peer answers as a yapitalism server before writing anything. A peer on a public address is refused unless allow_public is said explicitly; the tailnet is the transport, not the trust story — the peer's bearer token still decides who may call. Configured peers show up in yapitalism doctor with live pane counts.
Agents can be started and resumed on a peer too: panes_create and panes_resume take a machine argument naming one. The peer runs its own full gate chain — and starting an agent remotely is more authority than typing into one, so it has its own switch, off by default: yapitalism authority allow-remote-create, once, on the peer. To keep a peer's server alive across reboots, yapitalism service --host prints a filled launchd plist or systemd unit; installing it stays your decision.
Voice cannot say mbp3:tmux:%2. Bind a word to a pane once —
panes_name("billing", "tmux:%4")
— and every tool accepts billing from then on. The binding records what the pane runs at name-time and is re-verified against a live listing on every use: tmux reuses pane ids, so a name whose pane vanished or changed runtime is refused with the reason, never silently retargeted. No fuzzy matching — "probably the right codex" is not a target. Names appear on their panes in panes_list.
The bridge agent behaves best with standing instructions — speak receipts, never resend a YELLOW, name panes like a person. The exact prompt we run is in docs/operator-prompt.md; paste it into your voice client's custom instructions.
The six tools compose into watchers worth having: a permission watch (nothing waits on a dialog silently — its first real catch was an agent silently holding a wallet-transaction approval), a provider-outage watch, an end-of-day digest. Working prompts in docs/recipes.md.
Needs Python 3.11+ and tmux, on macOS or Linux — the full send-and-prove loop is exercised on a bare python:3.11-slim container per release, not just assumed portable. Everything runs on your machine; nothing is exposed to the network.
# 1. install
pipx install yapitalism # or: uv tool install yapitalism / pip install yapitalism
yapitalism-mcp
codex mcp add yapitalism --url http://127.0.0.1:8792/mcp
yapitalism setup
setup interviews the machine rather than printing "installed successfully": which backends are usable, which agent CLIs are on PATH, whether a Superset host is live and which build it is, and the guarantee table above filled in for you. It writes nothing except, if you sa