jarvis (omnigentx/jarvis) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 101 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

jarvis

Omnigentx Jarvis — voice + chat AI assistant powered by Fast Agent (MCP) with Vue dashboard. Single-user, self-hosted, multi-skill orchestration.

→ omnigentx/jarvis· listed on github_code

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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 pushwhy connect →

Who stands behind it

omnigentx

Source: github_code

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
🚨
Secret credentials may flow to a network call
1 flow detected: JARVIS_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 6 credentials: JARVIS_API_KEY, ROBOROCK_PASSWORD, JARVIS_MASTER_KEY, JWT_SECRET, CONFLUENCE_API_TOKEN, JARVIS_CF_TURN_API_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.
configPW_BASE_URL
configPW_PORT
configVITE_PORT
configVITE_PROXY_TARGET
🔐 secretJARVIS_API_KEY
configSPAWN_REGISTRY_DB
configSPAWN_EVENT_SOCKET
configJARVIS_RUNTIME_RPC_SOCKET
configJARVIS_TIMEZONE
configJARVIS_MAIN_PROCESS
configCORS_ORIGINS
configMCP_CONFIG
configMCP_ENDPOINT
configJARVIS_API_URL
configROBOROCK_USERNAME
🔐 secretROBOROCK_PASSWORD
configDISABLE_AGENT_SPAWNER
configJARVIS_DB_PATH
configLOG_LEVEL
configLOG_CONSOLE_LEVEL
🔐 secretJARVIS_MASTER_KEY
🔐 secretJWT_SECRET
configSPAWN_PROJECT_DIR
configTRUSTED_WS_ORIGINS
configJARVIS_VOICE_DIAG
configCONFLUENCE_URL
configCONFLUENCE_USERNAME
🔐 secretCONFLUENCE_API_TOKEN
configJARVIS_MASTER_KEY_OLD
configJARVIS_MASTER_KEY_NEW
configJARVIS_PERSIST_DIR
configGH_CONFIG_DIR
configJARVIS_WEBRTC_ICE
configJARVIS_CF_TURN_KEY_ID
🔐 secretJARVIS_CF_TURN_API_TOKEN
// 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

101/101 tools missing one or more hints — mcp_list_servers (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); mcp_get_server (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); mcp_create_server (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +98 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

35/101 tools referenced in tests (35%)

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

Secrets not logged

2 secret values sent to logger.info

Redact or omit secret values from log output.

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 Score](https://m8ven.ai/badge/mcp/omnigentx/jarvis)](https://m8ven.ai/mcp/omnigentx/jarvis)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 8666029a46f987c1b2e22cc9f440955b5cefe49f
code hash: 2732d5ab6dd7cf1c88762495a0fb9816d8e724c13824af8c15d646bcc81bc3f2
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