toss
MCPB · TOSS.MCPB
Send files to your own devices and friends, peer to peer and end-to-end encrypted.
Available components
Last scanned (22 hours ago)
Scores higher than 74% of MCPB 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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
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 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 323 tokens (~80/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 5 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
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.
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 40
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 4 Nov 2026 · Analysed mcpb/https://github.com/plamen-g/toss/releases/download/v0.3.2/toss.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
list_devices ~21
List the devices paired with toss. send_files takes these names.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
received_files ~45
List what arrived on this computer through toss lately, newest first: files from paired devices and from the phone page, with where they were saved. Open them with your own file tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
send_files ~112
Send files or folders to a paired device, end-to-end encrypted. Someone on the device accepts them first, unless it takes files from here without asking. Files from outside the folders the user lets you send from, and files that look like secrets, need the user's yes, which toss asks for. Only send what the user asked to send.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | The paired device to send to, as list_devices names it. |
| paths | array | yes | Absolute paths of the files and folders to send. |
No output schema declared.
No examples provided.
show_on_phone ~97
Offer files to the user's phone, with no app on the phone: toss's window shows a QR code, and the phone's camera opens a page that downloads them, over the same Wi-Fi as this computer. Files, not folders. As with send_files, only offer what the user asked for; toss asks the user first where needed.
| Name | Type | Req | Description |
|---|---|---|---|
| paths | array | yes | Absolute paths of the files to offer (files, not folders). |
No output schema declared.
No examples provided.
How do I install the toss MCP server?
toss ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 0f325919f20cb173fa5a3f9921b3a853930fd40c7ac0930be00494e4eb3968f0; the commands to do that are on this page. If it does not match, do not open it.
mcpb · toss.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
0f325919f20cb173fa5a3f9921b3a853930fd40c7ac0930be00494e4eb3968f0
macOS / Linux
echo "0f325919f20cb173fa5a3f9921b3a853930fd40c7ac0930be00494e4eb3968f0 toss.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\toss.mcpb).Hash -eq "0f325919f20cb173fa5a3f9921b3a853930fd40c7ac0930be00494e4eb3968f0"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the toss MCP server?
toss is an MCP server listed in the public MCP registry as io.github.plamen-g/toss. Send files to your own devices and friends, peer to peer and end-to-end encrypted. This page covers its MCPB bundle (https://github.com/plamen-g/toss/releases/download/v0.3.2/toss.mcpb).
Is the toss MCP server safe to use?
toss scores 43 out of 100 on VerifyMCP. 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 toss MCP server expose?
toss exposes 4 tools: list_devices, received_files, send_files, show_on_phone. Their descriptions and schemas cost roughly 275 tokens of context every time the server is loaded.
What licence is the toss MCP server under?
toss declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.