# io.github.hkturtco/qrfile (pypi · qrfile-mcp)

Send files automatically to Android over Wi-Fi, or share one-time HTTPS links and QR codes.

- Trust score: 68/100 (medium)
- Change this week: +18
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `qrfile-mcp`: 68/100 (this document), [markdown](https://verifymcp.io/servers/hkturtco-qrfile/qrfile-mcp.md), [page](https://verifymcp.io/servers/hkturtco-qrfile/qrfile-mcp)

## Channel facts

- Registry: `pypi`
- Package: `qrfile-mcp`
- Version: `0.2.11`
- 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**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - 2 of 34 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 6/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 17 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1289 tokens (~99/item across 13 items; 13 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 94/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 3 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_android_transfer" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does.
  - 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 current MCP spec version (2026-07-28).

## Install

### How do I install the io.github.hkturtco/qrfile MCP server?

io.github.hkturtco/qrfile runs locally as a PyPI package, launched with uvx qrfile-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 hkturtco-qrfile -- uvx qrfile-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "hkturtco-qrfile": {
      "command": "uvx",
      "args": [
        "qrfile-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "hkturtco-qrfile": {
      "command": "uvx",
      "args": [
        "qrfile-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add hkturtco-qrfile -- uvx qrfile-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hkturtco-qrfile": {
      "type": "local",
      "command": [
        "uvx",
        "qrfile-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add hkturtco-qrfile --command uvx --arg qrfile-mcp
```

### Hermes

```yaml
mcp_servers:
  hkturtco-qrfile:
    command: "uvx"
    args: ["qrfile-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "hkturtco-qrfile": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "qrfile-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add hkturtco-qrfile -t stdio -c uvx -a qrfile-mcp
```

### Other

```json
{
  "mcpServers": {
    "hkturtco-qrfile": {
      "command": "uvx",
      "args": [
        "qrfile-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-05 (score 68, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-04 (score 53, −14)

- [security regression] Malware scan: pass → unverified

### 2026-11-02 (score 67, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 51, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 50, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 49, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-26 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (13)

### `list_local_networks` (~28 tokens)

List private IPv4 LAN interfaces. Use an interface name only if automatic selection needs correction.

### `create_file_share` (~201 tokens)

Send explicitly user-requested files to their phone or other local device.

Supply exact absolute paths, not directories. Copies only those files into an isolated temporary
HTTPS server and returns a credential-bearing URL, temporary user ID/password, expiry, QR image
and TLS certificate fingerprint/trust instructions. TLS 1.2 or newer is required.
The link downloads directly (one ZIP for multiple files) and closes after one complete send.
No receiving app, manual login, upload, account or cloud service is required.
Default self-signed certificates cause browser warnings; verify the fingerprint and configure
receiver certificate trust. For warning-free use, supply a certificate the receiver trusts.
Both devices must be on the same private IPv4 subnet; keep the MCP host running during transfer.
expires_in_seconds is the deadline to start downloading; an accepted download may finish afterward.

Input parameters:

- `expires_in_seconds` (integer)
- `file_paths` (array, required)
- `interface`

### `list_file_shares` (~26 tokens)

Show share status, expiration, file names and completed download counts without exposing passwords.

### `get_file_share` (~36 tokens)

Recover an active share's URL and QR code, or inspect its expiration/revocation status.

Input parameters:

- `share_id` (string, required)

### `revoke_file_share` (~32 tokens)

Immediately stop a temporary server, invalidate its credentials and remove its staged files.

Input parameters:

- `share_id` (string, required)

### `start_android_pairing` (~170 tokens)

Start a five-minute pairing session and SHOW THE QR IMAGE for the phone to scan.

Ask the user to open QRFile, turn on Receiving, tap Scan pairing QR code then Scan QR,
and scan this QR. For another PC: Settings > Paired PCs > Pair another PC.
Then check get_android_pairing. The phone displays four digits: ask the user
to type them into this chat and WAIT for their answer before confirming. No device
is saved until that human-provided code matches. Pair one phone per QR.
pc_name optionally sets the sender's friendly name shown on the phone; otherwise
the PC's hostname is used. device_name names the target phone, not this PC.

Input parameters:

- `device_name` (string, required)
- `interface`
- `pc_name`

### `get_android_pairing` (~77 tokens)

Check whether a phone scanned the pairing QR. When waiting_confirmation, ASK the user
for the four digits displayed on their phone. Never guess or derive the code.
After displaying the QR, set wait_seconds=30 to wait for a scan without polling.

Input parameters:

- `pairing_id` (string, required)
- `wait_seconds` (integer)

### `confirm_android_pairing` (~72 tokens)

Confirm with the exact four-digit string the HUMAN just supplied from the phone.

Preserve leading zeros. Never guess, derive, autofill, or retry a different code
without new human input. Five incorrect attempts close the session.

Input parameters:

- `confirmation_code` (string, required)
- `pairing_id` (string, required)

### `cancel_android_pairing` (~32 tokens)

Cancel an unfinished pairing, close its listener, and invalidate its QR.

Input parameters:

- `pairing_id` (string, required)

### `list_android_devices` (~19 tokens)

List paired Android inbox devices without exposing pairing keys.

### `forget_android_device` (~39 tokens)

Forget a device on this PC when the user requests it. Reset pairing on the phone to revoke all PCs.

Input parameters:

- `device_name` (string, required)

### `send_file_to_android` (~116 tokens)

Send only explicitly requested files directly to a paired Android phone's private inbox.

Requires receiving enabled and the same LAN. No browser or QR scanning is needed after
pairing. Multiple files arrive as one ZIP. The phone verifies the pinned HTTPS certificate,
length and SHA-256 before reporting received. Use get_android_transfer to confirm receipt;
queued or server-side completion does not prove the phone saved and verified the file.

Input parameters:

- `device_name`
- `expires_in_seconds` (integer)
- `file_paths` (array, required)

### `get_android_transfer` (~37 tokens)

Ask the paired phone whether a delivery is queued, downloading, received/verified, saved or failed.

Input parameters:

- `transfer_id` (string, required)

## Diagnostics

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

## Score history

- 2026-11-05: 68
- 2026-11-04: 53
- 2026-11-03: 67
- 2026-11-02: 67
- 2026-11-01: 51
- 2026-10-31: 51
- 2026-10-30: 50
- 2026-10-29: 50
- 2026-10-28: 49
- 2026-10-27: 64
- 2026-10-26: 64
- 2026-10-25: 63
- 2026-10-24: 63
- 2026-10-23: 62
- 2026-10-22: 62
- 2026-10-21: 61
- 2026-10-20: 61
- 2026-10-19: 60
- 2026-10-18: 31
- 2026-10-17: 44
- 2026-10-16: 59
- 2026-10-15: 59
- 2026-10-14: 31
- 2026-10-13: 31

## Common questions

### What is the io.github.hkturtco/qrfile MCP server?

io.github.hkturtco/qrfile is an MCP server listed in the public MCP registry as io.github.hkturtco/qrfile. Send files automatically to Android over Wi-Fi, or share one-time HTTPS links and QR codes. This page covers its PyPI package (qrfile-mcp).

### Is the io.github.hkturtco/qrfile MCP server safe to use?

io.github.hkturtco/qrfile scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 io.github.hkturtco/qrfile MCP server expose?

io.github.hkturtco/qrfile exposes 13 tools: list_local_networks, create_file_share, list_file_shares, get_file_share, revoke_file_share, and 8 more. Their descriptions and schemas cost roughly 885 tokens of context every time the server is loaded.

### Is the io.github.hkturtco/qrfile MCP server still maintained?

io.github.hkturtco/qrfile 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.

## Links

- PyPI project: https://pypi.org/project/qrfile-mcp/
- Socket report: https://socket.dev/pypi/package/qrfile-mcp
- Changelog RSS feed: https://verifymcp.io/servers/hkturtco-qrfile/qrfile-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/hkturtco-qrfile/qrfile-mcp.json
- HTML version of this page: https://verifymcp.io/servers/hkturtco-qrfile/qrfile-mcp