Behalf (PXP v0) MCP Server

by julesnsenda Your server? Claim it

answering

Behalf (PXP v0) is answering right now. Last checked 9 min ago. It exposes 8 tools. Last commit 25 Oct 2026.

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

Uptime history 33 days of history · worst day 99%

33 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

177 ms

Response time

average over 24h

Stars

last commit 25 Oct 2026

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 10 October 2026. No other catalogue keeps this.

10 Oct a tool description was rewritten create_room

10 Oct a tool changed version

What the code does

We read the source, 6 d ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Builds a file path from a variable test-support/paths.js:10, test-support/fake-page.js:61, test-support/server.js:81

function readRepo(f) { return fs.readFileSync(path.join(ROOT, f), 'utf8'); }

Runs an external command test-support/server.js:36

  const child = spawn(process.execPath, [...args, entry], { env: baseEnv(env), shell: false, stdio: ['ignore', 'pipe', 'pipe'] });

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://behalf.dropkit.sh/mcp

~/.codex/config.toml

[mcp_servers.behalf]
url = "https://behalf.dropkit.sh/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "behalf": {
      "url": "https://behalf.dropkit.sh/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "behalf": {
      "type": "http",
      "url": "https://behalf.dropkit.sh/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

room

create_room

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_room

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

answer

answer_escalation

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.

brief

get_brief

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

join

join_room

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

seal_intent_card

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

send

send_envelope

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

wait_for_turn

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.

Endpoints

URL	Transport	State	Latency	Checked
https://behalf.dropkit.sh/mcp	streamable-http	answering	167 ms	9 min ago

Alternatives to Behalf (PXP v0)

same job, measured the same way

Attest

by dev-prathap

Decide by policy, gate behind a human, verify by read-back, record a hash-chained ledger.

local only

Attest proxy

by dev-prathap

Zero-code proxy: policy, human gate, read-back and a hash-chained ledger for any MCP server.

88 installs/wk local only

Hub

by spelunking

Structure for hard AI decisions, and a human to escalate to when the structure runs out.

7 tools answering

Pre-dispatch rejection ledger

by textforagents

Witness for MCP calls rejected pre-dispatch: hash-chained ledger, enum differ, signed receipts.

3 tools answering

SHA-256 Hash-Chained AI Agent Compliance & Decision Notary

by ceadigital

Tamper-evident SHA-256 hash-chained decision notary for EU AI Act, NIST AI RMF & SOC2.

28 tools answering

unbrowser by Unchained

by protostatis

Chrome-free MCP web access for agents with low-token page maps and browser escalation hints.

434 installs/wk local only

Grideōs Facts

by grideos

Read-only facts about Grideōs from its signed, hash-chained ledger. Verify before you cite.

7 tools answering

Ghostmotion

by ghostmotion

Create and edit product videos from a brief: launch, demo and feature films, rendered for you.

answering

Behalf (PXP v0) — questions

Answers built from our own checks of this server.

What can Behalf (PXP v0) do?

It exposes 8 tools, read directly from the server on our last check. Among them: answer_escalation, create_room, get_brief, get_room, join_room, seal_intent_card and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Behalf (PXP v0) working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 177 ms. The bar chart above shows every period we have measured.

How do I connect Behalf (PXP v0)?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Behalf (PXP v0) need an API key?

No. Behalf (PXP v0) completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Behalf (PXP v0)?

It answers our handshake in 177 ms on average, which is faster than 77% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Behalf (PXP v0) open source?

We cannot say either way: written in JavaScript and 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.