Behalf (PXP v0)

Name: Behalf (PXP v0)
Author: JulesNsenda

作者：JulesNsenda版本 0.2.0i★ –i在云端运行

注册名称io.github.JulesNsenda/behalf

安装

概览

作者提供的说明（英文原文）

Negotiate for your human under PXP: tagged claims, escalation, decision brief, hash-chained ledger

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在云端运行
传输方式: Streamable HTTP
分类: 会计、财务与税务
你需要填写：Authorization

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
需要你自己填写： Authorization

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

在终端中运行这条命令

claude mcp add --transport http behalf https://behalf.dropkit.sh/mcp --header 'Authorization: your-value'

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "behalf": {
      "url": "https://behalf.dropkit.sh/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "behalf": {
      "type": "http",
      "url": "https://behalf.dropkit.sh/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

Authorization 机密 HTTP header
Needed only to create a room: "Bearer ". Get a key at https://behalf.dropkit.sh after signing in with GitHub. Joining a room with a seat link needs no key.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 JulesNsenda 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
… 尚未检查
端点有响应
尚未检查；我们会轮流检查各个端点
… 尚未检查
使用 OAuth 登录
尚未检查；我们会轮流检查各个端点
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“会计、财务与税务”中的其他服务器比较i

星标数多于此分类中其他 2898 个服务器的 0%
发布到注册中心的时间比此分类中其他 2898 个服务器的 51% 更新
基础检查结果等于或优于此分类中其他 2898 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Behalf (PXP v0) 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：Authorization

它在我的电脑上运行还是在云端？

它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.2.0）于32天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Finance Toolkit, SolidInvoice, Korea Tax Calculator

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Finance Toolkit

作者：JerBouma

500+ transparent financial methods calculated from raw statements, not third-party endpoints.

电脑或云端★ 5,496MIT昨天更新

安装

SolidInvoice

作者：SolidInvoice

Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.

在云端运行★ 981MIT8天前更新

安装

Korea Tax Calculator

作者：UpstageAI

Korean tax calculation and tax-audit judgment MCP: 96 tools with statutory citations.

在你的电脑上运行★ 97MIT昨天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Behalf

Reference implementation of PXP v0, the Proxy Exchange Protocol: two AI proxies negotiate for two people, every claim is tagged stated / sourced / assumed, proxies escalate to their humans at a limit, and every agreement ships with a decision brief and a hash-chained ledger.

Based on the essay *Agentic Proxies: When Humans Become Routing Nodes* by Jules Nsenda.

spec/ — a copy of the protocol (SPEC.md + JSON schemas). The canonical spec is JulesNsenda/pxp, published at https://julesnsenda.github.io/pxp/
lib/pxp.js — protocol core: sealing, envelope enforcement, ledger
lib/proxy.js — Claude-backed proxies
lib/demo.js — scripted demo (hallucination cascade), runs with no API key
lib/mcp.js — MCP endpoint at /mcp, so any MCP-capable agent can take a seat
lib/auth.js, lib/http-auth.js — GitHub sign-in and agent keys
lib/ai-access.js — "Use our AI" access: who may spend the built-in Claude (lib/durable.js is the save bookkeeping it shares with lib/auth.js)
lib/mail.js — email: one sendMail over a dev outbox or SMTP (lib/mail-dev.js, lib/mail-smtp.js). See MAIL.md
index.js — the Node server (Node 20+). Its dependencies are pg, loaded only when DATABASE_URL is set, and nodemailer, loaded only when MAIL_TRANSPORT=smtp
web/ — the pages:
Home (/)
Start (/start): create a room, then invite the other person
Room (/room/:id): instructions, then the conversation
Agreement (/brief/:id)
Connect (/connect): use your own AI agent, and create its agent key
Admin (/admin): the owner approves "Use our AI" requests
Protocol (/spec)
web/ui/ — the zero-dependency UI library; its living style guide is at /ui
test/ — npm test (node:test). The Postgres tests run only when PG_TEST_URL is set

Config

Env	Default	Purpose
`ANTHROPIC_API_KEY`	none	Enables built-in Claude proxies, card drafting and the authority audit. Without it, the demo and bring-your-own-agent rooms still work
`PXP_MODEL`	`claude-sonnet-5-5`	Model for proxies
`ROOM_PASSCODE`	none	Only when `SIGNIN=off`: if set, creating a live room requires it, and ten wrong guesses lock an address out for the day. With `SIGNIN=github` it is ignored (`/api/config` reports `passcode: false`): a signed-in person, or a valid agent key, needs no passcode, no wrong guess is counted, and boot logs the warning `app.passcode_ignored` and keeps running
`DAILY_ROOM_LIMIT`	20	Live rooms per day, all users together. Admins and people with "Use our AI" access are exempt from it and their rooms do not count toward it, so free accounts cannot use it up on them (an admin is still held to `ADMIN_DAILY`, 50 a day)
`PER_IP_DAILY`	3	With `SIGNIN=off`, live rooms per day per address
`PER_USER_DAILY`	3	With `SIGNIN=github`, live rooms per day per account. A signed-in person is limited by this and `DAILY_ROOM_LIMIT` only, not by their address
`MAX_TURNS`	10	Proxy turns before a room stalls
`PUBLIC_URL`	`https://behalf.dropkit.sh`	Base URL used in seat links handed to agents. With sign-in on, it must be `https` (plain `http` only for `localhost`): its origin is what the browser's `Origin` header must match, and it forms the GitHub callback URL
`PORT`	3000	Listen port. `0` picks a free port, and the startup log prints the one it bound
`BIND_HOST`	all interfaces	Address to bind, e.g. `127.0.0.1`. It isn't called `HOST`, because some shells set `HOST` to the machine name
`ROOM_TTL_DAYS`	30	A live room is deleted after this many days without activity. Its links then show the room as gone
`DEMO_TTL_HOURS`	24	The same, for demo rooms
`MAX_ROOMS`	5000	Upper bound on stored rooms. When a new room would go past it, the server makes room down to 95%: demo rooms go first, oldest first, then finished live rooms. A live room still in progress is never deleted
`TRUST_PROXY`	`private`	When to trust `X-Forwarded-For` for the client IP. Choices: `never`; `loopback` (only when the peer is this machine, which is the safest choice when the proxy runs on the same host); `private` (a loopback or private-network peer, such as the platform's proxy); or `always`. `private` assumes no untrusted host on that network can reach the app port directly. Per-IP limits group IPv6 clients by /64. The server logs `net.xff_ignored` once if a forwarded header arrives from an untrusted peer: that is a spoof attempt, or a proxy outside the trusted set
`SIGNIN`	`off` locally	`github` or `off`. Required whenever `DROP_DATA_DIR` or `DATABASE_URL` is set: without it the server refuses to start (`BAD_SIGNIN`). With `off` there is no sign-in, and anyone (or anyone with the passcode, if one is set) can open live rooms. With `github`, opening a live room needs a GitHub account
`GITHUB_CLIENT_ID`, `GITHUB_CLIENT_SECRET`	none	Secrets of your GitHub OAuth app. Both are required when `SIGNIN=github` (`BAD_SIGNIN_SECRETS` otherwise). The server reads them once and removes them from its environment
`GITHUB_BLOCKED_IDS`	none	Comma-separated numeric GitHub user ids that may not sign in. Their existing sessions and agent keys stop working at once
`ADMIN_GITHUB_IDS`	none	Comma-separated numeric GitHub user ids of the owner(s). They always have "Use our AI" access, decide other people's requests on `/admin`, and have their own daily cap of `ADMIN_DAILY` live rooms (50, a constant in `lib/rooms.js`, not a setting) instead of `PER_USER_DAILY`. Set it in the Drop dashboard only (it is not in `drop.yaml`); changing it needs a restart. With `SIGNIN=github`, the built-in AI on and none set, the server logs the warning `app.no_admins` and keeps running: nobody could approve a request
`ADMIN_EMAIL`	none	One address that gets an email when someone makes a new "Use our AI" request. The email says "A GitHub user, @login," asked (linked to their GitHub page) and links to `/admin`; it does not include their note, which you read on `/admin`. At most 20 an hour and 50 a day: a held-back one is not sent, and each email says how many requests are waiting then (`mail.notify_capped` is logged once). Set it in the Drop dashboard only (it is not in `drop.yaml`). It needs mail that can be delivered: `MAIL_TRANSPORT=smtp`, or the dev transport off the platform on a local `PUBLIC_URL`. On the platform, or on a public `PUBLIC_URL`, the dev transport doesn't deliver (its outbox is a folder nobody can read), so with it (or with sign-in off) the server logs the warning `mail.admin_email_unused` at boot and sends nothing. If `smtp` is not verified when a request arrives, the notice is skipped and `mail.notice_skipped` is logged once. Never shown in `/api/config` or `/health`
`REQUIRE_DATABASE`	`0`, or `1` when `DROP_DATA_DIR` is set	`1` or `0`. With `1` the server exits at startup (`BAD_REQUIRE_DATABASE`, before it binds the port) when `DATABASE_URL` is not set, instead of falling back to an empty `rooms.json`. It is on by default on Drop, so the guard holds even if no setting reaches the app; `0` turns it off on purpose
`DATABASE_URL`	none	A Postgres URL. When set, rooms and accounts live in Postgres instead of `rooms.json`. Configure the connection only through this URL: don't set the other `PG*` variables. It must be a direct or session-mode connection, not a transaction pooler (`EPOOLER`). The server logs `store.no_tls` if a non-local URL doesn't ask for TLS, or turns off certificate checks
`MAIL_TRANSPORT`	`dev`	`dev` or `smtp`. `dev` sends nothing: each email is written to `DROP_DATA_DIR/outbox` (or `./.data/outbox`), and, off the platform with `PUBLIC_URL` unset or on localhost only, listed at `/dev/outbox`. `smtp` sends through your SMTP server. See MAIL.md
`MAIL_FROM`	none	The sender, `Name` or a bare address, e.g. `Behalf` . Required with `smtp`. Your SMTP server must be allowed to send for its domain
`SMTP_HOST`, `SMTP_PORT`	none	Your SMTP server. Required with `smtp`
`SMTP_SECURE`	follows the port	`true` (TLS from the start, port 465) or `false` (STARTTLS, port 587). TLS is required either way: the password never crosses a plain connection. `465` with `false` and `587` with `true` are refused (`BAD_SMTP_SECURE`)
`SMTP_USER`, `SMTP_PASS`	none	Secrets: the SMTP login. Required with `smtp` (`BAD_SMTP_AUTH`). Read once and removed from the environment
`DRAIN_DEADLINE_MS`	4000	On `SIGTERM` or `SIGINT`, how long the server may spend saving before it exits. 100 to 9000. Keep it below the time your platform allows between the stop signal and a forced kill (Drop: 5 s under PM2, 10 s under Docker). The Postgres statement timeout is 3 s, so one write fits

ROOM_TTL_DAYS, DEMO_TTL_HOURS, MAX_ROOMS, TRUST_PROXY, SIGNIN, PER_USER_DAILY, GITHUB_BLOCKED_IDS, ADMIN_GITHUB_IDS, ADMIN_EMAIL, DRAIN_DEADLINE_MS, REQUIRE_DATABASE and the mail variables are strict: an invalid value stops the server at startup with BAD_ , and the log names the variable but never its value. ROOM_TTL_DAYS, DEMO_TTL_HOURS and MAX_ROOMS must be whole numbers from 1 up to 3650, 87600 and 1,000,000; PER_USER_DAILY from 1 to 1000. Each room also has an AI allowance of MAX_TURNS × 3 Claude calls, and drafting a card doesn't count toward it. A room that uses it up ends with no deal, like reaching the turn limit.

Inviting by email

With SIGNIN=github and mail that can reach a person (MAIL_TRANSPORT=smtp, or the dev transport off the platform on a local PUBLIC_URL: see MAIL.md), the invite step of /start has an optional "Their email" field. The email carries the other seat's private link, with a fixed subject and text: it names the sender only as "A GitHub user, @login", and holds no names or topic. Behalf never stores the address or logs it: it is held only for that one send, and, for the 3-a-day count, as a keyed hash in memory. The one exception is the dev outbox, which holds the whole email (so the address and the link) and exists only on a local machine. Limits: 3 invites per room, 10 per person and 50 per day across everyone (admins and people with "Use our AI" access don't count toward the 50), and 3 a day to the same address (the usual spellings of one mailbox, such as Jane.Doe+news@gmail.com and janedoe@googlemail.com, share it). These caps are a trade-off: they stop Behalf being used to spam one person, but they also let someone use up an address's 3 for the day (or the 50 for everyone) without ever reaching it, and the owner then has to copy the link instead. A seat B link sent by email can be sent to up to 3 addresses per room, and anyone holding the link is that seat. Past a limit the page says so and the owner can copy the link instead. Deploy: on Drop, invites need SMTP (MAIL_TRANSPORT=smtp and the settings in MAIL.md). Until then /api/config reports invite: false, the field is hidden, and a direct request gets 503 mail_off.

Startup refusals

The server stops at startup, and logs one line with a code, rather than run in a state that could lose data. If it stops, look for store.load_failed or app.init_failed in the log:

Code	Meaning
`BAD_SIGNIN`	`SIGNIN` is missing on the platform, or isn't `github` or `off`
`BAD_SIGNIN_SECRETS`	`SIGNIN=github` without both GitHub secrets
`BAD_PUBLIC_URL`	`SIGNIN=github` with a `PUBLIC_URL` that isn't https (or http on localhost)
`BAD_ADMIN_EMAIL`	`ADMIN_EMAIL` is not a single plain address

| BAD_SMTP_HOST, BAD_SMTP_PORT, BAD_SMTP_AUTH, BAD_MAIL_FROM, BAD_SMTP_SECURE | MAIL_TRANSPORT=smtp with a setting missing or invalid, or a port and TLS mode that don't go together. A server that can't be reached or refuses the login does not stop startup: the

只显示了开头部分；其余内容请在仓库中阅读