onsense (hufirst/onsense) is an MCP server listed on the M8ven Trust Index. It scores 69 out of 100, grade C. It declares 7 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Limited view
69/100

onsense

Gives PC AI agents real-world senses by connecting to an Android phone's camera, sensors, and files over local Wi-Fi without cloud relay or ADB.

→ hufirst/onsense· listed on glama

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

hufirst

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: PHONE_TOKEN, ONSENSE_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretPHONE_TOKEN(from pairing) Pairing auth token
configONSENSE_HOME
configONSENSE_CLIP_ALLOW_PULL0 Set to 1 to enable PC→phone pull without the CLI flag
configONSENSE_CLIP_SET_CLIPBOARD0 Set to 1 to auto-inject into OS clipboard without the CLI flag
configONSENSE_CLIP_ALLOW_REMOTE_SETTINGS
🔐 secretONSENSE_TOKEN
configONSENSE_CLIP_DIRImages are saved to disk as latest.jpg (in , default <tempdir>/onsense/).
configONSENSE_CLIP_MAX_MB200 Maximum incoming file size in MB (0 = unlimited)
configWAYLAND_DISPLAY
configDISPLAY
configXDG_CURRENT_DESKTOP
configPHONE_BASE(from pairing) Phone HTTP base URL, e.g. http://192.168.1.5:8080
configONSENSE_FROM
configONSENSE_TEST_FRAME(unset) Local JPEG path returned by get_live_frame when phone is unreachable
configONSENSE_SERVE_DEDUP
configONSENSE_SERVE_ALLOW_DUPLICATES
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

7/7 tools missing one or more hints — get_live_frame (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); read_sensors (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); recent_photos (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

Only 3/7 tool handlers declare input schemas (43%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

4/7 tool handlers wrap calls in try/catch (57%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/hufirst/onsense)](https://m8ven.ai/mcp/hufirst/onsense)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 69e4c86fcec6c597d9e1173b0d34efeebf261506
code hash: bc448af26aa8e37131ece59e03eb0459717020271a4db2e7d4a23a455ddad687
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client