Behalf (PXP v0)

Name: Behalf (PXP v0)
Author: JulesNsenda

de JulesNsendaversión 0.2.0i★ –iSe ejecuta en la nube

Nombre en el registroio.github.JulesNsenda/behalf

Instalar

Resumen

Descripción del creador (original en inglés)

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

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Opinión de usuariosiAún no hay reseñasLas reseñas se abrirán junto con las cuentas en una etapa posterior
Nuestras revisiones básicasi1 de 1 superadasRevisado con información pública; el código aún no se ha escaneado
UsoiAún sin medir★ –

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

Conexión: Se ejecuta en la nube
Transporte: Streamable HTTP
Categoría: Contabilidad, finanzas e impuestos
Debes completar: Authorization

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

Revisiones básicas: 1 de 1 superadas
Se ejecuta en el servidor del creador: lo que le pidas pasa por su servidor.
Debes completar tú: Authorization

Los valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.

Necesitas

Se ejecuta en la nubeNo hay nada que instalar; se conecta por internet

¿Qué app usas?

ClaudeClaude CodeCursorVS CodeChatGPT

Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.

Esta dirección necesita una clave en un header de la solicitud, y el menú para agregar conectores no puede ponerla. Usa Claude Code, Cursor o VS Code.

Ejecuta esto en tu terminal

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

Completa los valores vacíos antes de ejecutarlo.

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json

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

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

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

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Esta dirección necesita una clave en un header de la solicitud, y el menú para agregar conectores no puede ponerla. Usa Claude Code, Cursor o VS Code.

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Valores que debes completar

Authorization secreto 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.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Todavía no hemos leído la lista de herramientas de este servidor; revisamos los endpoints por turnos.

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026

✓ Superada
El creador coincide con el repo
El nombre en el registro se verificó con la cuenta de GitHub JulesNsenda, dueña del repo
… Aún sin revisar
Sigue en mantenimiento
Todavía no hemos leído este repo en GitHub
… Aún sin revisar
Tiene licencia
Todavía no hemos leído este repo en GitHub
… Aún sin revisar
El endpoint responde
Aún sin revisar; revisamos los endpoints por turnos
… Aún sin revisar
Inicio de sesión con OAuth
Aún sin revisar; revisamos los endpoints por turnos
… Aún sin revisar
Sin instrucciones ocultas en las descripciones de herramientas
Aún sin revisar; leemos la lista de herramientas cuando revisamos el endpoint

Comparado con otros en Contabilidad, finanzas e impuestosi

Más estrellas que el 0% de los otros 1734 servidores de esta categoría
Publicado en el registro más recientemente que el 56% de los otros 1734 servidores de esta categoría
Revisiones básicas iguales o mejores que el 100% de los otros 1734 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro Behalf (PXP v0)?

Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

Debes completar: Authorization

¿Se ejecuta en mi computadora o en la nube?

Se ejecuta en la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (0.2.0) llegó al registro hace 31 días.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.

¿Qué puedo usar en su lugar?

En la misma categoría: Finance Toolkit, SolidInvoice, Korea Tax Calculator

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

Finance Toolkit

de JerBouma

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

Computadora o nube★ 5496MITActualizado hoy

Instalar

SolidInvoice

de SolidInvoice

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

Se ejecuta en la nube★ 981MITActualizado hace 8 días

Instalar

Korea Tax Calculator

de UpstageAI

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

Se ejecuta en tu computadora★ 97MITActualizado ayer

Instalar

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

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

Solo se muestra el principio; lee el resto en el repo

Behalf (PXP v0)

Resumen

Los tres pilares de PopNx MCP

Qué puedes hacer con él

Instalación

Antes de instalar

Valores que debes completar

Qué puede hacer

Revisiones básicasi

El creador coincide con el repo

Sigue en mantenimiento

Tiene licencia

El endpoint responde

Inicio de sesión con OAuth

Sin instrucciones ocultas en las descripciones de herramientas

Comparado con otros en Contabilidad, finanzas e impuestosi

Preguntas frecuentes

Alternativas

Finance Toolkit

SolidInvoice

Korea Tax Calculator

README del creador

Behalf

Config

Inviting by email

Startup refusals