# PairOnce (npm · paironce)

Send files and text between an AI agent and your own paired devices, end-to-end encrypted.

- Trust score: 78/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `paironce`: 78/100 (this document), [markdown](https://verifymcp.io/servers/paironce-cli/paironce.md), [page](https://verifymcp.io/servers/paironce-cli/paironce)

## Channel facts

- Registry: `npm`
- Package: `paironce`
- Version: `0.9.1`
- 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-05.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 1 of 20 dependencies flagged as unhealthy (1 deprecated).
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to paironce/cli).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1329 tokens (~132/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability observed for 0 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 96% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_file" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 10 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 PairOnce MCP server?

PairOnce runs locally as an npm package, launched with npx -y paironce. 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 paironce-cli -- npx -y paironce
```

### Cursor

```json
{
  "mcpServers": {
    "paironce-cli": {
      "command": "npx",
      "args": [
        "-y",
        "paironce"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "paironce-cli": {
      "command": "npx",
      "args": [
        "-y",
        "paironce"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add paironce-cli -- npx -y paironce
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add paironce-cli --command npx --arg -y --arg paironce
```

### Hermes

```yaml
mcp_servers:
  paironce-cli:
    command: "npx"
    args: ["-y", "paironce"]
```

### Netclaw

```json
{
  "McpServers": {
    "paironce-cli": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "paironce"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add paironce-cli -t stdio -c npx -a -y paironce
```

### Other

```json
{
  "mcpServers": {
    "paironce-cli": {
      "command": "npx",
      "args": [
        "-y",
        "paironce"
      ]
    }
  }
}
```

## 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-05 (score 78)

First indexed and scored.

## MCP tools (10)

### `pair_device` (~165 tokens)

Pair one of the user's devices (phone or computer) with this agent through PairOnce; needed once per device. Three calls. First call: returns a six-digit code; tell the user to open https://paironce.com on that device, choose "Enter a code" and type it. Second call: waits until they did and returns a safety code; ask the user whether their device shows the same one. Third call: confirm true if they said yes, false if not. Never confirm without asking the user.

Input parameters:

- `confirm` (boolean): Third call: whether the user said their device shows the same safety code.
- `wait_seconds` (number): Second call: how long to wait for the user to type the code, 120 by default, at most 600.

### `list_devices` (~20 tokens)

List the devices this agent is paired with through PairOnce.

### `send_file` (~90 tokens)

Send files from this computer to one of the user's paired devices through PairOnce, end-to-end encrypted. The user accepts each file on that device, and PairOnce must be open there.

Input parameters:

- `device` (string): Name of a paired device (from list_devices). Optional when only one is paired.
- `paths` (array, required): Files to send (absolute paths, or relative to the server's folder).

### `send_text` (~67 tokens)

Send a message or a link to one of the user's paired devices through PairOnce, end-to-end encrypted. PairOnce must be open there.

Input parameters:

- `device` (string): Name of a paired device (from list_devices). Optional when only one is paired.
- `text` (string, required)

### `receive_files` (~149 tokens)

Wait for the user to send files (photos, scans, documents) from one of their paired devices, and save them into a folder here. Tell the user to open https://paironce.com on that device, tap Connect, then choose the files. Returns the saved paths and any messages the user sent.

Input parameters:

- `device` (string): Name of a paired device (from list_devices). Optional when only one is paired.
- `folder` (string): Where to save: a relative path inside the server's folder, with no folder starting with a dot. Default: inbox.
- `wait_seconds` (number): How long to wait for the user, 120 by default, at most 600.

### `request_photo` (~179 tokens)

Ask the user for a photo from one of their paired devices (usually their phone), for example of a label, a screen, an error message or a document. Their device shows your request with your reason; they take the photo there and it is saved here (default ./inbox). They may decline.

Input parameters:

- `device` (string): Name of a paired device (from list_devices). Optional when only one is paired.
- `folder` (string): Where to save: a relative path inside the server's folder, with no folder starting with a dot. Default: inbox.
- `purpose` (string, required): What you need and why, in one or two sentences the user reads on their device (at most 300 characters).
- `wait_seconds` (number): How long to wait for the user, 120 by default, at most 600.

### `request_scan` (~168 tokens)

Ask the user to scan paper pages with one of their paired devices (usually their phone): it makes a PDF there with straightened pages, which is saved here (default ./inbox). Their device shows your request with your reason. They may decline.

Input parameters:

- `device` (string): Name of a paired device (from list_devices). Optional when only one is paired.
- `folder` (string): Where to save: a relative path inside the server's folder, with no folder starting with a dot. Default: inbox.
- `purpose` (string, required): What you need and why, in one or two sentences the user reads on their device (at most 300 characters).
- `wait_seconds` (number): How long to wait for the user, 120 by default, at most 600.

### `request_file` (~160 tokens)

Ask the user for a file from one of their paired devices: their device shows your request with your reason, they choose the file there, and it is saved here (default ./inbox). They may decline.

Input parameters:

- `device` (string): Name of a paired device (from list_devices). Optional when only one is paired.
- `folder` (string): Where to save: a relative path inside the server's folder, with no folder starting with a dot. Default: inbox.
- `purpose` (string, required): What you need and why, in one or two sentences the user reads on their device (at most 300 characters).
- `wait_seconds` (number): How long to wait for the user, 120 by default, at most 600.

### `watch_frames` (~306 tokens)

See what the user sees: ask to watch their camera or screen on one of their paired devices, then get still pictures of it, returned as images you can look at (and saved, default ./inbox/watch). The first call asks; their device shows your reason and they share the camera or the screen there, or decline. Later calls return new stills from the same share, so you can guide them step by step ("now turn the switch on the left"). It ends when they stop, when you call watch_stop, or after 5 minutes without a call; their device ends it after 15 minutes.

Input parameters:

- `count` (number): Stills to take now, 1 to 5. Default 1.
- `device` (string): Name of a paired device (from list_devices). Optional when only one is paired.
- `folder` (string): Where to save the stills: a relative path inside the server's folder, with no folder starting with a dot. Default: inbox/watch.
- `interval_seconds` (number): Seconds between those stills, 0.5 to 10. Default 1.
- `purpose` (string): Needed when not watching yet: what you want to see and why, in one or two sentences the user reads on their device (at most 300 characters).
- `wait_seconds` (number): When asking: how long to wait for the user to share, 120 by default, at most 600.

### `watch_stop` (~25 tokens)

Stop watching the user's camera or screen (see watch_frames). Their device stops sharing.

## Diagnostics

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

## Score history

- 2026-11-05: 78

## Common questions

### What is the PairOnce MCP server?

PairOnce is an MCP server listed in the public MCP registry as io.github.paironce/cli. Send files and text between an AI agent and your own paired devices, end-to-end encrypted. This page covers its npm package (paironce).

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

PairOnce scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 PairOnce MCP server expose?

PairOnce exposes 10 tools: pair_device, list_devices, send_file, send_text, receive_files, and 5 more. Their descriptions and schemas cost roughly 1,329 tokens of context every time the server is loaded.

### Is the PairOnce MCP server still maintained?

PairOnce is still listed as active in the MCP registry. We last reached this channel on 5 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 PairOnce MCP server under?

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

## Links

- npm package: https://www.npmjs.com/package/paironce
- Socket report: https://socket.dev/npm/package/paironce
- Repository: https://github.com/paironce/cli
- Website: https://paironce.com/
- Changelog RSS feed: https://verifymcp.io/servers/paironce-cli/paironce.xml
- Changelog JSON feed: https://verifymcp.io/servers/paironce-cli/paironce.json
- HTML version of this page: https://verifymcp.io/servers/paironce-cli/paironce