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

C
Emerging
74/100

remy

Native iOS remote for a fleet of Claude Code tmux sessions, over Tailscale

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

padamchopra

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 →

Install from

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
2 flows detected: REMY_API_TOKEN, REMY_APNS_KEY_ID. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 2 credentials: REMY_API_TOKEN, REMY_APNS_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.
configComSpec
configMC_CONFIG_DIR
configPROGRAMFILES
configPROGRAMFILES(X86)
configREMY_AGENT_ID
🔐 secretREMY_API_TOKEN
configREMY_API_URL
configREMY_APNS_BUNDLE_ID
🔐 secretREMY_APNS_KEY
configREMY_APNS_KEY_ID
configREMY_APNS_KEY_PATH
configREMY_APNS_PRODUCTION
configREMY_APNS_TEAM_ID
configREMY_BROWSER_EXECUTABLE
configREMY_CHAT_DM
configREMY_CHAT_ID
configREMY_DEVICE_ID
configREMY_MCP_PROVIDER
configSHELL
configTERM
// quality suggestions

Dependencies

8 runtime dependencies (3 dev), 1 flagged: playwright-core

Tool annotations

32/34 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

10/34 tools missing one or more hints — list_workspaces (missing: idempotentHint); browser_snapshot (missing: idempotentHint); browser_wait (missing: idempotentHint), +7 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.

openWorldHint matches behaviour

5 tools claim openWorldHint=false but make outbound HTTP — register_workspace → dynamic (line 89); create_ticket → dynamic (line 89); update_ticket → dynamic (line 89)

Either flip openWorldHint to true (acknowledging external reach) or refactor the handler to avoid outbound HTTP. If the only network calls are to a known fixed endpoint that you consider part of the tool itself, document that and keep openWorldHint=false; otherwise true is honest.

README present

No README found

Add a README.md describing the server and its tools.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 2/34 tools referenced in tests (6%)

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

Shell command execution

22 calls in production code run through a shell (src/discovery.ts:71, src/discovery.ts:203, src/tailnet.ts:52)

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

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

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 8 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/padamchopra/remy)](https://m8ven.ai/mcp/padamchopra/remy)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: ab3bcc7dfdfa6accc9e5705a11d167ba54cbf758
code hash: 4f88374241eb3480bb0ea44d887ac6341a02045a7ae4aac87795bc03d17f5319
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