io.github.hufirst/onsense
PYPI · ONSENSE · SCANNED SEP 23
Android phone camera, sensors & files for any MCP client — local, no cloud, no ADB.
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 Security48
- Malware scan not yet available for this package.Unverified
- Known CVEs were checked across the 36 of 38 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- Dependency health was assessed across the 36 of 38 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency48
- 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 42 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability29
- AI-judged instruction clarity (poor).Fail
- Tool/resource definitions use about 841 tokens (~105/item across 8 items; 8 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 Coverage71
- 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
- Structured output schemas are declared (75% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- Manipulation check failed: an AI judge found 1 of 8 captured unit(s) of tool text manipulative, the first being "tool: get_reference". See how to fix → Fail
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.hufirst/onsense MCP server?
io.github.hufirst/onsense runs locally as a PyPI package, launched with uvx onsense. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · onsense
claude mcp add hufirst-onsense -- uvx onsense
{
"mcpServers": {
"hufirst-onsense": {
"command": "uvx",
"args": [
"onsense"
]
}
}
} {
"servers": {
"hufirst-onsense": {
"command": "uvx",
"args": [
"onsense"
]
}
}
} codex mcp add hufirst-onsense -- uvx onsense
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"hufirst-onsense": {
"type": "local",
"command": [
"uvx",
"onsense"
],
"enabled": true
}
}
} openclaw mcp add hufirst-onsense --command uvx --arg onsense
mcp_servers:
hufirst-onsense:
command: "uvx"
args: ["onsense"] {
"McpServers": {
"hufirst-onsense": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"onsense"
]
}
}
} assistant mcp add hufirst-onsense -t stdio -c uvx -a onsense
{
"mcpServers": {
"hufirst-onsense": {
"command": "uvx",
"args": [
"onsense"
]
}
}
} 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.
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 22 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.
- 20 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 19 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 18 Sept 26 −2
- Stability: pass → 0.83 functional
- 17 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 16 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 15 Sept 26 0
- Package version: 0.3.19 → 0.3.20 functional
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 23 Sept 2026 · Analysed pypi/onsense@0.3.20
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 | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 36 packages
| Packages resolved | 36 |
|---|---|
| Stale | 2 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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 →
get_cam_fps ~35
Query the phone's current camera FPS setting (15=high performance, 2=balanced, 0=on-demand).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_live_frame ~36
One current frame from the phone camera (JPEG). Falls back to a local test image (if configured) when the phone is unreachable.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_photo ~279
Fetch the photo for the id returned by recent_photos, AND save it on the PC. Returns the image + {"path"} JSON. The save is the point: an image that only lands in the conversation is gone once the session ends, so the user cannot find it again later. Every fetched photo is written to the same folder as get_reference (the user's Downloads folder), never a temp folder. The file is first named photo_<id>.jpg — a placeholder. After you look at the image, ALWAYS call rename_photo(path, "<what it actually shows>") so the user can find it by name later (e.g. "whiteboard meeting notes", "receipt 2026-08"). You have already seen the image at that point, so naming costs nothing extra — never fetch it a second time just to name it. save_original=True re-fetches at the highest resolution the phone will serve, for archival (two phone fetches, slower); the default saves exactly the downscaled bytes you were shown. Note this is NOT necessarily the camera-roll original: the free tier caps every image transfer at 720p (long edge 1280 / short edge 720), the same limit as capture.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
| max_width | integer | – | – |
| save_original | boolean | – | – |
No output schema declared.
No examples provided.
get_reference ~183
Download whatever the phone currently designates as the 'share target' to the PC, save it, and return the path and metadata (JSON). Depends on the phone app's reference mode: LIVE = real-time camera frame, Capture = a fixed captured image, File = an arbitrary file the user chose. Non-image files (PDF, video, documents, etc.) are fetched as-is too. (If you only need an image preview, get_live_frame is simpler.) Returns: {"path", "mime", "bytes", "name"} — path is the PC-local save path (the user's Downloads folder, so it's easy to find and use later — not a temp folder). Always call this to fetch the phone's CURRENT designation — never reuse files already sitting in the save folder (they are stale copies from earlier fetches, not what the user has designated now).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
read_sensors ~33
The phone's current sensor values (battery level/charging, illuminance lux, acceleration x/y/z) as JSON.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
recent_photos ~82
JSON list of the device's recent photos (id, name, date_added, w, h). Get the image via get_photo(id). If the user designated content in the phone app (LIVE / Capture / File / Phone clipboard), prefer get_reference — it returns exactly what they picked; this gallery list may not include it.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
rename_photo ~129
Rename a file fetched by get_photo/get_reference to a name describing what the image ACTUALLY shows. Call this right after looking at a fetched image — photo_<id>.jpg tells the user nothing when they open the folder weeks later. Describe the content ("whiteboard sprint plan", "parking receipt"), do not restate the id. The extension is kept; a date prefix is fine. Collisions get a _2, _3 suffix rather than overwriting. Only files inside the onSense folder can be renamed.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_cam_fps ~64
Change the phone's camera FPS setting. fps: 2 (balanced, recommended), 0 (power-saving/on-demand). 15 (high performance) is a Pro feature — on the free tier the phone caps it to 2.
| Name | Type | Req | Description |
|---|---|---|---|
| fps | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the io.github.hufirst/onsense MCP server?
io.github.hufirst/onsense is an MCP server listed in the public MCP registry as io.github.hufirst/onsense. Android phone camera, sensors & files for any MCP client, local, no cloud, no ADB. This page covers its PyPI package (onsense).
Is the io.github.hufirst/onsense MCP server safe to use?
io.github.hufirst/onsense scores 57 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 io.github.hufirst/onsense MCP server expose?
io.github.hufirst/onsense exposes 8 tools: get_live_frame, read_sensors, recent_photos, get_photo, get_reference, and 3 more. Their descriptions and schemas cost roughly 841 tokens of context every time the server is loaded.
Is the io.github.hufirst/onsense MCP server still maintained?
io.github.hufirst/onsense is still listed as active in the MCP registry. We last reached this channel on 23 September 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.hufirst/onsense MCP server under?
io.github.hufirst/onsense declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.