MCP.Market

Behalf (PXP v0) MCP server

online · 96% uptime
by JulesNsenda·io.github.JulesNsenda/behalf·v0.2.0
No reviews yet

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

A88/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Behalf (PXP v0) yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Behalf (PXP v0) tools (8, 2 write)

write = sends, deletes, buys or posts
  • answer_escalationFree

    When the room is paused for your principal, ask them the question verbatim and relay their exact answer. It is sealed into their card as an amendment. Never answer on their behalf.

  • create_roomwrite actionFree

    Open a new room. Your principal takes seat A, and you get a private invite link for the other person (seat B). Send the invite only to that person. Use this when your principal wants to negotiate with someone and has no room yet. This server requires sign-in: your MCP client must send your principal's agent key as an Authorization: Bearer header (not as an argument). Your principal gets a key at https://behalf.dropkit.sh/key. No passcode is needed. counterpart_proxy "builtin" also needs "Use our AI" access, which your principal asks for at https://behalf.dropkit.sh/start; without it, use "external".

  • get_briefFree

    The decision brief once the room has ended: agreed terms, authority per term, unverified assumptions, escalations, ledger head.

  • get_roomFree

    Current state from your seat: status, whose turn, transcript, claims you still need to review, unverified assumptions, and the next action.

  • join_roomFree

    Take your principal's seat with their private link. Returns the room state, your principal's card (if sealed), and what to do next.

  • seal_intent_cardFree

    Seal your principal's Intent Card. Only after they confirmed every line. Once sealed it cannot change except through escalation answers.

  • send_envelopewrite actionFree

    Send one PXP envelope on your turn. The server enforces the rules: untagged or unreferenced claims become "assumed", agreeing while raising a conflict is refused. The enforced envelope is returned.

  • wait_for_turnFree

    Blocks up to timeout_seconds (max 25) until it is your turn, your principal must answer a question, or the room ends. Call it again if it times out.

Public scan report

scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1819ms20/20
  • Tool poisoning8 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 6 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Behalf (PXP v0) compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
Tools
8
the typical server has 7
Tools that change things
25%
typical: 0%. Fewer write tools means less an agent can break
Uptime
96%
of our recent checks; the typical remote server answers 100%
Response time
845 ms
faster than 15% of 30,031 servers

What its tools let an agent do: 6 read · 1 create · 1 send or post

Install Behalf (PXP v0) in Claude Code, Cursor or VS Code

claude mcp add --transport http behalf https://behalf.dropkit.sh/mcp
Add to Cursor

What the publisher says

From the Behalf (PXP v0) repository's README, as published. We do not edit it. Read it on GitHub

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 DATABASEURL is set, and nodemailer, loaded only when MAILTRANSPORT=smtp
  • web/ — the pages:
  • Home (/)
  • Start (/start): create a room, then invite the other person

Config

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Behalf (PXP v0): common questions

Is Behalf (PXP v0) MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Behalf (PXP v0) safety report
How do I install Behalf (PXP v0)?
It runs remotely at behalf.dropkit.sh. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Behalf (PXP v0) need an API key?
Yes. The registry entry asks for Authorization.
Is Behalf (PXP v0) maintained?
The last commit was 27 days ago (2026-10-08). The latest release is v0.2.0.
Is Behalf (PXP v0) up?
96% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Behalf (PXP v0) compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); tools 8 (the typical server has 7); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.