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

Back to MCP Trust IndexM8ven
C
Emerging
74/100
11 days ago

MobileOps

→ Rustyadj/MobileOps· 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

Rustyadj

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
✅
31 tools verified — handlers match their declared behaviour
11 read-only tools verified — handlers contain no write/delete/exec
✅
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 8 credentials: JWT_SECRET_KEY, JWT_REFRESH_SECRET_KEY, ADMIN_PASSWORD, HERMES_MCP_TOKEN, HERMES_NATHAN_GATEWAY_TOKEN, TWILIO_AUTH_TOKEN, TWILIO_API_KEY_SECRET, OPENAI_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.
configEXPO_PUBLIC_BACKEND_URL
configEXPO_PUBLIC_DEMO_MODE
configMETRO_CACHE_ROOT
configMONGO_URL
configDB_NAME
🔐 secretJWT_SECRET_KEY
🔐 secretJWT_REFRESH_SECRET_KEY
configACCESS_TOKEN_EXPIRE_MIN
configREFRESH_TOKEN_EXPIRE_DAYS
configADMIN_EMAIL
🔐 secretADMIN_PASSWORD
configSIGNUP_ALLOWED_DOMAINS
configSIGNUP_INVITE_CODES
🔐 secretHERMES_MCP_TOKEN
configHERMES_MCP_TOKEN_SHA256
configHERMES_MCP_TOKEN_SHA256_FILE
configHERMES_MCP_SCOPES
configMCP_ISSUER_URL
configMCP_ALLOWED_ORIGINS
configHERMES_NATHAN_GATEWAY_URL
🔐 secretHERMES_NATHAN_GATEWAY_TOKEN
configHERMES_NATHAN_CONNECT_HOST
configHERMES_NATHAN_CONNECT_PORT
configHERMES_NATHAN_PROFILE
configHERMES_NATHAN_TIMEOUT_SECONDS
configTWILIO_ACCOUNT_SID
🔐 secretTWILIO_AUTH_TOKEN
configTWILIO_API_KEY_SID
🔐 secretTWILIO_API_KEY_SECRET
configTWILIO_PHONE_NUMBER
🔐 secretOPENAI_API_KEY
configVOICE_PUBLIC_BASE_URL
configVOICE_REALTIME_MODEL
configVOICE_REALTIME_FULL_MODEL
configVOICE_REALTIME_VOICE
configVOICE_TRANSCRIPTION_MODEL
// quality suggestions

Tool test coverage

18/31 tools referenced in tests (58%)

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

Shell command execution

7 calls in production code run through a shell (frontend/src/db/sqlite.ts:48, frontend/src/db/sqlite.ts:52, frontend/src/db/sqlite.ts:60)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

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 2 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/rustyadj/mobileops)](https://m8ven.ai/mcp/rustyadj/mobileops)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 61d4fe60a9313bc5e9fbce599df2d2e979d0956f
code hash: d2f5a9b4e94a3bf481782a617f0d9b2e8f8a3791265afbb070ca3641a1c80601
verified: 9/2/2026, 6:44:23 PM
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