io.github.LofiFren/picocalc-mcp
PYPI · PICOCALC-MCP
AI assistant access to PicoCalc MicroPython hardware over USB.
Available components
Last scanned (20 minutes ago)
Scores higher than 82% of PyPI servers
Category IoT and Hardware
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 Security99
- 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
- 1 of 5 dependencies flagged as unhealthy. 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 222 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 302 tokens (~50/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "picocalc_exec" implies "exec" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.97 functional
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Provenance: unverified → fail ▼ security
- 24 Oct 26 0
- Provenance: fail → unverified ▼ security
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 6 Nov 2026 · Analysed pypi/picocalc-mcp@0.1.1
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 | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 5 packages
| Packages resolved | 5 |
|---|---|
| Stale | 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 →
picocalc_exec ~69
Execute MicroPython code on the PicoCalc device. Returns stdout and stderr. Use for testing, debugging, reading sensors, or running one-off commands. 30 second timeout -- do not use for launching apps with main loops.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Python code to execute on the device |
No output schema declared.
No examples provided.
picocalc_list_files ~50
List files on the PicoCalc device at a given path. Returns file names, types, and sizes.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Device directory path (default: /sd/py_scripts) |
No output schema declared.
No examples provided.
picocalc_push ~85
Push a local file to the PicoCalc device. The local_path is relative to the MicroPython/ directory in the project.
| Name | Type | Req | Description |
|---|---|---|---|
| local_path | string | yes | Local file path relative to MicroPython/ dir (e.g. sd/py_scripts/my_app.py) |
| remote_path | string | yes | Device path (e.g. /sd/py_scripts/my_app.py) |
No output schema declared.
No examples provided.
picocalc_read_file ~46
Read a file from the PicoCalc device and return its contents.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Device file path (e.g. /sd/py_scripts/synth.py) |
No output schema declared.
No examples provided.
picocalc_reset ~26
Soft reset the PicoCalc device. Re-runs boot.py and main.py.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
picocalc_status ~26
Check PicoCalc device connection status, RAM, SD card, and firmware version.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.LofiFren/picocalc-mcp server?
io.github.LofiFren/picocalc-mcp runs locally as a PyPI package, launched with uvx picocalc-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 · picocalc-mcp
claude mcp add lofifren-picocalc-mcp -- uvx picocalc-mcp
What is the io.github.LofiFren/picocalc-mcp server?
io.github.LofiFren/picocalc-mcp is listed in the public MCP registry as io.github.LofiFren/picocalc-mcp. AI assistant access to PicoCalc MicroPython hardware over USB. This page covers its PyPI package (picocalc-mcp).
Is the io.github.LofiFren/picocalc-mcp server safe to use?
io.github.LofiFren/picocalc-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 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.LofiFren/picocalc-mcp server expose?
io.github.LofiFren/picocalc-mcp exposes 6 tools: picocalc_status, picocalc_exec, picocalc_push, picocalc_list_files, picocalc_read_file, picocalc_reset. Their descriptions and schemas cost roughly 302 tokens of context every time the server is loaded.
Is the io.github.LofiFren/picocalc-mcp server still maintained?
io.github.LofiFren/picocalc-mcp is still listed as active in the MCP registry. We last reached this channel on 6 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 io.github.LofiFren/picocalc-mcp server under?
io.github.LofiFren/picocalc-mcp 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 io.github.LofiFren/picocalc-mcp server?
VerifyMCP ran 16 checks on io.github.LofiFren/picocalc-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.