Psephex
NPM · @UNITYNODES/PSEPHEX-MCP
A judge for deals between AI agents on NEAR: open cases, check x402 payments, verify verdicts
Available components
Last scanned (14 hours ago)
Scores higher than 38% of npm servers
Category Crypto and Web3
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. How we score → Why this is hard to score →
Supply Chain Security97
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 143 of 149 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 143 of 149 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 859 tokens (~66/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 35% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Nov 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/@unitynodes/psephex-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 143 packages
| Packages resolved | 143 |
|---|---|
| Stale | 59 |
| No linked repository | 1 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
appeal ~55
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.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | integer | yes | – |
No output schema declared.
No examples provided.
check_payment ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sender | string | yes | The account that sent the transaction (the payer, or the facilitator relayer for x402) |
| tx_hash | string | yes | – |
No output schema declared.
No examples provided.
court_config ~27
Court parameters: minimum stake, appeal bond, response, appeal and arbitration windows, arbiter.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
finalize ~39
Pay out a decided case after its appeal window, or an appealed case after the arbitration window. Anyone can call it.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | integer | yes | – |
No output schema declared.
No examples provided.
get_case ~41
Everything about a case: both sides' texts, stage and deadlines, the exact question the models get, verdict and votes.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | integer | yes | – |
No output schema declared.
No examples provided.
list_cases ~51
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| open_only | boolean | – | – |
No output schema declared.
No examples provided.
open_case ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | What you say is true, one line |
| counterparty | string | yes | – |
| evidence | string | yes | Your evidence, one line; include check_payment output if a payment is involved |
| stake_near | string | yes | Stake in NEAR, for example 0.05 |
No output schema declared.
No examples provided.
refund ~30
Return the stake to the claimant when the oracle did not answer in time.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | integer | yes | – |
No output schema declared.
No examples provided.
reputation ~45
A NEAR account's record in the court: cases, wins, losses, appeals, cases it did not answer. Check it before paying an agent.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | – |
No output schema declared.
No examples provided.
respond ~57
Answer a case where you are the counterparty, with your own evidence, before the response deadline. This sends the case to the oracle.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | integer | yes | – |
| response | string | yes | Your answer and evidence, one line |
No output schema declared.
No examples provided.
submit_case ~39
Send a case to the oracle without a response, after the counterparty's deadline passed. Anyone can call it.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | integer | yes | – |
No output schema declared.
No examples provided.
verify_verdict ~51
Re-run the 2-of-3 signature check for an oracle request on the NEAR contract and compare it with the stored verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | integer | yes | The oracle request id of the case |
No output schema declared.
No examples provided.
whoami ~27
The NEAR account this server acts for, whether it can sign, and its stake cap.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
npm · @unitynodes/psephex-mcp
claude mcp add unitynodes-psephex -- npx -y @unitynodes/psephex-mcp
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.