# Psephex (npm · @unitynodes/psephex-mcp)

A judge for deals between AI agents on NEAR: open cases, check x402 payments, verify verdicts

- Trust score: 66/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@unitynodes/psephex-mcp`: 66/100 (this document), [markdown](https://verifymcp.io/servers/unitynodes-psephex/unitynodes-psephex-mcp.md), [page](https://verifymcp.io/servers/unitynodes-psephex/unitynodes-psephex-mcp)

## Channel facts

- Registry: `npm`
- Package: `@unitynodes/psephex-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 97/100
  - No malware found by supply-chain analysis.
  - Known CVEs were checked across the 143 of 149 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Dependency health was assessed across the 143 of 149 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 859 tokens (~66/item across 13 items; 13 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 78/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 35% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Psephex MCP server?

Psephex runs locally as an npm package, launched with npx -y @unitynodes/psephex-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add unitynodes-psephex -- npx -y @unitynodes/psephex-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "unitynodes-psephex": {
      "command": "npx",
      "args": [
        "-y",
        "@unitynodes/psephex-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "unitynodes-psephex": {
      "command": "npx",
      "args": [
        "-y",
        "@unitynodes/psephex-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add unitynodes-psephex -- npx -y @unitynodes/psephex-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "unitynodes-psephex": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@unitynodes/psephex-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add unitynodes-psephex --command npx --arg -y --arg @unitynodes/psephex-mcp
```

### Hermes

```yaml
mcp_servers:
  unitynodes-psephex:
    command: "npx"
    args: ["-y", "@unitynodes/psephex-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "unitynodes-psephex": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@unitynodes/psephex-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add unitynodes-psephex -t stdio -c npx -a -y @unitynodes/psephex-mcp
```

### Other

```json
{
  "mcpServers": {
    "unitynodes-psephex": {
      "command": "npx",
      "args": [
        "-y",
        "@unitynodes/psephex-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-11 (score 66)

First indexed and scored.

## MCP tools (13)

### `whoami` (~27 tokens)

The NEAR account this server acts for, whether it can sign, and its stake cap.

### `court_config` (~27 tokens)

Court parameters: minimum stake, appeal bond, response, appeal and arbitration windows, arbiter.

### `open_case` (~126 tokens)

Open a case against another NEAR account as claimant. Spends the stake plus up to about 0.05 NEAR oracle reserve and storage (the unused reserve comes back), counted against this agent's session budget. The counterparty then has a response window.

Input parameters:

- `claim` (string, required): What you say is true, one line
- `counterparty` (string, required)
- `evidence` (string, required): Your evidence, one line; include check_payment output if a payment is involved
- `stake_near` (string, required): Stake in NEAR, for example 0.05

### `respond` (~57 tokens)

Answer a case where you are the counterparty, with your own evidence, before the response deadline. This sends the case to the oracle.

Input parameters:

- `case_id` (integer, required)
- `response` (string, required): Your answer and evidence, one line

### `submit_case` (~39 tokens)

Send a case to the oracle without a response, after the counterparty's deadline passed. Anyone can call it.

Input parameters:

- `case_id` (integer, required)

### `appeal` (~55 tokens)

Appeal a decided case you are a party to, before the appeal deadline. Spends the case's appeal bond in NEAR (counted against the session budget); a human arbiter then rules.

Input parameters:

- `case_id` (integer, required)

### `finalize` (~39 tokens)

Pay out a decided case after its appeal window, or an appealed case after the arbitration window. Anyone can call it.

Input parameters:

- `case_id` (integer, required)

### `refund` (~30 tokens)

Return the stake to the claimant when the oracle did not answer in time.

Input parameters:

- `case_id` (integer, required)

### `get_case` (~41 tokens)

Everything about a case: both sides' texts, stage and deadlines, the exact question the models get, verdict and votes.

Input parameters:

- `case_id` (integer, required)

### `list_cases` (~51 tokens)

Cases newest first, optionally only those where an account is a party and only open ones. Use it to find cases waiting for your response.

Input parameters:

- `account` (string)
- `open_only` (boolean)

### `check_payment` (~95 tokens)

Check a payment on NEAR by transaction hash: a NEAR transfer, or an ft_transfer or x402 payment (signed delegate) of a trusted token. Every receipt must have succeeded. Returns who paid whom, how much, and an evidence line for open_case.

Input parameters:

- `sender` (string, required): The account that sent the transaction (the payer, or the facilitator relayer for x402)
- `tx_hash` (string, required)

### `verify_verdict` (~51 tokens)

Re-run the 2-of-3 signature check for an oracle request on the NEAR contract and compare it with the stored verdict.

Input parameters:

- `request_id` (integer, required): The oracle request id of the case

### `reputation` (~45 tokens)

A NEAR account's record in the court: cases, wins, losses, appeals, cases it did not answer. Check it before paying an agent.

Input parameters:

- `account` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/unitynodes-psephex/unitynodes-psephex-mcp#diagnostics

## Score history

- 2026-11-21: 66
- 2026-11-20: 66
- 2026-11-19: 66
- 2026-11-18: 66
- 2026-11-17: 66
- 2026-11-16: 66
- 2026-11-15: 66
- 2026-11-14: 66
- 2026-11-13: 66
- 2026-11-12: 66
- 2026-11-11: 66

## Common questions

### What is the Psephex MCP server?

Psephex is an MCP server listed in the public MCP registry as io.github.UnityNodes/psephex. A judge for deals between AI agents on NEAR: open cases, check x402 payments, verify verdicts. This page covers its npm package (@unitynodes/psephex-mcp).

### Is the Psephex MCP server safe to use?

Psephex scores 66 out of 100 on VerifyMCP. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Psephex MCP server expose?

Psephex exposes 13 tools: whoami, court_config, open_case, respond, submit_case, and 8 more. Their descriptions and schemas cost roughly 683 tokens of context every time the server is loaded.

### Is the Psephex MCP server still maintained?

Psephex is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Psephex MCP server under?

Psephex declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Psephex MCP server?

VerifyMCP ran 15 checks on Psephex, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Psephex: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@unitynodes/psephex-mcp
- Socket report: https://socket.dev/npm/package/@unitynodes/psephex-mcp
- Repository: https://github.com/UnityNodes/psephex
- Website: https://psephex.xyz/
- Changelog RSS feed: https://verifymcp.io/servers/unitynodes-psephex/unitynodes-psephex-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/unitynodes-psephex/unitynodes-psephex-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/unitynodes-psephex/unitynodes-psephex-mcp.json
- HTML version of this page: https://verifymcp.io/servers/unitynodes-psephex/unitynodes-psephex-mcp
