io.github.LofiFren/picocalc-mcp
PYPI · PICOCALC-MCP · SCANNED SEP 21
AI assistant access to PicoCalc MicroPython hardware over USB.
Available components
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 Security49
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 5 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 176 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 Management93
- Stability observed for 28 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 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
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
{
"mcpServers": {
"lofifren-picocalc-mcp": {
"command": "uvx",
"args": [
"picocalc-mcp"
]
}
}
} {
"servers": {
"lofifren-picocalc-mcp": {
"command": "uvx",
"args": [
"picocalc-mcp"
]
}
}
} codex mcp add lofifren-picocalc-mcp -- uvx picocalc-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lofifren-picocalc-mcp": {
"type": "local",
"command": [
"uvx",
"picocalc-mcp"
],
"enabled": true
}
}
} openclaw mcp add lofifren-picocalc-mcp --command uvx --arg picocalc-mcp
mcp_servers:
lofifren-picocalc-mcp:
command: "uvx"
args: ["picocalc-mcp"] {
"McpServers": {
"lofifren-picocalc-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"picocalc-mcp"
]
}
}
} assistant mcp add lofifren-picocalc-mcp -t stdio -c uvx -a picocalc-mcp
{
"mcpServers": {
"lofifren-picocalc-mcp": {
"command": "uvx",
"args": [
"picocalc-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −18
- Malware scan: pass → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.80 functional
- 16 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +15
- Malware scan: unverified → pass ▲ 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 21 Sept 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 |
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 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.
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 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.