io.github.hkturtco/qrfile
PYPI · QRFILE-MCP
Send files automatically to Android over Wi-Fi, or share one-time HTTPS links and QR codes.
Available components
Last scanned (5 hours ago)
Scores higher than 64% of PyPI servers
Category Documents and Files
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 2 of 34 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 17 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1289 tokens (~99/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 Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety94
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Partial
- 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 current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 2 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 28 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 26 Oct 26 +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.
- 24 Oct 26 +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.
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 5 Nov 2026 · Analysed pypi/qrfile-mcp@0.2.11
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 34 packages
| Packages resolved | 34 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
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 →
cancel_android_pairing ~32
Cancel an unfinished pairing, close its listener, and invalidate its QR.
| Name | Type | Req | Description |
|---|---|---|---|
| pairing_id | string | yes | – |
No output schema declared.
No examples provided.
confirm_android_pairing ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_code | string | yes | – |
| pairing_id | string | yes | – |
No output schema declared.
No examples provided.
create_file_share ~201
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.
| Name | Type | Req | Description |
|---|---|---|---|
| expires_in_seconds | integer | – | – |
| file_paths | array | yes | – |
| interface | – | – | – |
No output schema declared.
No examples provided.
forget_android_device ~39
Forget a device on this PC when the user requests it. Reset pairing on the phone to revoke all PCs.
| Name | Type | Req | Description |
|---|---|---|---|
| device_name | string | yes | – |
No output schema declared.
No examples provided.
get_android_pairing ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pairing_id | string | yes | – |
| wait_seconds | integer | – | – |
No output schema declared.
No examples provided.
get_android_transfer ~37
Ask the paired phone whether a delivery is queued, downloading, received/verified, saved or failed.
| Name | Type | Req | Description |
|---|---|---|---|
| transfer_id | string | yes | – |
No output schema declared.
No examples provided.
get_file_share ~36
Recover an active share's URL and QR code, or inspect its expiration/revocation status.
| Name | Type | Req | Description |
|---|---|---|---|
| share_id | string | yes | – |
No output schema declared.
No examples provided.
list_android_devices ~19
List paired Android inbox devices without exposing pairing keys.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_file_shares ~26
Show share status, expiration, file names and completed download counts without exposing passwords.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_local_networks ~28
List private IPv4 LAN interfaces. Use an interface name only if automatic selection needs correction.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
revoke_file_share ~32
Immediately stop a temporary server, invalidate its credentials and remove its staged files.
| Name | Type | Req | Description |
|---|---|---|---|
| share_id | string | yes | – |
No output schema declared.
No examples provided.
send_file_to_android ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| device_name | – | – | – |
| expires_in_seconds | integer | – | – |
| file_paths | array | yes | – |
No output schema declared.
No examples provided.
start_android_pairing ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| device_name | string | yes | – |
| interface | – | – | – |
| pc_name | – | – | – |
No output schema declared.
No examples provided.
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.
pypi · qrfile-mcp
claude mcp add hkturtco-qrfile -- uvx qrfile-mcp
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.