PersonalJarvis (PersonalJarvis/PersonalJarvis) is an MCP server listed on the M8ven Trust Index. It scores 41 out of 100, grade D. It declares 16 tools. No publisher has claimed this listing.

Warning

41/100

PersonalJarvis

Item: PersonalJarvis
Rating: 41
Author: M8ven

Self-hosted voice assistant. Speak to your computer: it answers aloud, types your dictation, and operates your apps.

→ PersonalJarvis/PersonalJarvis · listed on github_repo_search

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

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 push why connect →

Who stands behind it

PersonalJarvis

Source: github_repo_search

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

GitHub

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

🚨

Reads files from sensitive locations

Touches: ~/.claude/.credentials.json

🔐

You'll be asked for 6 credentials: JARVIS_MCP_TOKEN, JARVIS_CONTROL_KEY, ADMIN_TOKEN, JARVIS_CONNECTOR_TOKEN, ANTHROPIC_OAUTH_TOKEN, ANTHROPIC_API_KEY

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.

configJARVIS_SCREEN_RUNNER_LOG

configJARVIS_VOICE

configJARVIS_BOOT_PROFILE

configJARVIS_ISOLATION_ROOT

configJARVIS_PRIMARY_INSTANCE

configJARVIS_DEBUG

configJARVIS_MCP_CALL_TIMEOUT_S

configJARVIS_MCP_CONFIG

configJARVIS_DATA_DIR

configJARVIS_API_URL

🔐 secretJARVIS_MCP_TOKEN

🔐 secretJARVIS_CONTROL_KEY

configXDG_CONFIG_HOME

configBACKEND_URL

🔐 secretADMIN_TOKEN

configProgramFiles

configProgramW6432

configDISPLAY

configWAYLAND_DISPLAY

🔐 secretJARVIS_CONNECTOR_TOKEN

configJARVIS_CONNECTOR_AUTH_TYPE

configCONDUCTOR_DB_PATH

configJARVIS_INSTALL_NO_PIP

configCLAUDE_CONFIG_DIR

configCODEX_HOME

configGROK_HOME

configKEYPROXY_DB_PATH

configJARVIS_CONFIG

configJARVIS_DESKTOP_BENCH_PORT

configJARVIS_DESKTOP_BENCH_MODE

🔐 secretANTHROPIC_OAUTH_TOKEN

🔐 secretANTHROPIC_API_KEY

configPYTHONIOENCODING

// quality suggestions

Tool annotations

2/16 tools have annotations

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

All four hints declared on every tool

16/16 tools missing one or more hints — memory_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memory_recent (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memory_add_fact (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +13 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 test coverage

Only 1/16 tools referenced in tests (6%)

Write tests that reference each tool by name so every tool has at least one test.

No access to sensitive paths

Reads sensitive paths: ~/.claude/.credentials.json

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

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 4 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 Verified](https://m8ven.ai/badge/mcp/personaljarvis/personaljarvis?variant=verified)](https://m8ven.ai/mcp/personaljarvis/personaljarvis)

Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.

commit: 66aed436380bff359a13151c31d2afadb2eb37cc

code hash: e1f00f74ca4f749379a8dabeb15069024dac13f90f85c555924d1210efcdfd94

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