VendorOnline Solution
Connects overstdio

Our grade: 4 checks

Login Login required, broad access
Upkeep Active · 2026-10
Known bugs 0 open
Connection stdio

Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.

Community rating

3.2 20 reviews
25% would trust it in production
  • 5 2
  • 4 5
  • 3 7
  • 2 6
  • 1 0

Trust in production

  • Trust it - 25%
  • With caveats - 25%
  • Wouldn't - 50%

50% would recommend this server

How reviewers scored it

  • Setup & docs 3.0
  • Auth experience 3.3
  • Reliability 3.3
  • Maintainer responsiveness 3.9

Why it got a C

An Apache-2.0 relay and npm package from Online Solution. Its main tool, remote_exec, lets your agent run any shell command it writes on a remote machine, as the user who pasted a one-line listener there, with no SSH port or agent install; two more tools show and reset the session. The plain one-liner starts supervised mode, which shows each command and waits for y/N on the remote. The auto line runs every command with no prompt, and the server tells the model to offer both, so choose supervised unless the host is disposable. By default commands and output pass through the free hosted relay at relay.remotify.run, which keeps them on disk until three hours idle, serves the listener script you pipe into bash, and can change the wording the model reads in tool results. It has no terms or privacy policy beyond its landing page and sends no HSTS header. Self-hosting is one docker compose command, but the shipped defaults are plain HTTP. The 128-bit session key is the only credential: anyone who sees the one-liner (shell history, a shared screen) can send commands until the session expires or you rotate it. One npm maintainer; no advisories on record. Biggest deduction: the tool runs model-written shell commands on another machine, and approval is optional and set on the remote, not by the server.

How to connect

// ~/.cursor/mcp.json
{ "mcpServers": { "remotify": { "command": "npx", "args": ["-y", "remotify-mcp@latest"] } } }

Is Remotify MCP safe?

Is Remotify MCP safe to use?

Remotify MCP grades C (usable with care). Each relay session uses a randomly generated session key, and anyone holding that key can queue commands for the session. There are no user accounts and no per-command permissions. In supervised mode the remote machine still has to approve each command, so keep the key secret and rotate it with remote_session_reset. Upkeep is hard to verify (closed source or a single maintainer), so pin the version you tested. It can run model-controlled code or uses a plaintext remote connection, so run it isolated with no credentials.

Does Remotify MCP have known vulnerabilities?

Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.

Does Remotify MCP support authentication?

Yes, but not a per-person login. Each relay session uses a randomly generated session key, and anyone holding that key can queue commands for the session. There are no user accounts and no per-command permissions. In supervised mode the remote machine still has to approve each command, so keep the key secret and rotate it with remote_session_reset.

Embed this badge

Maintain this server? Add the grade to your README.

TrustedMCP grade C

Markdown

[![TrustedMCP grade C](https://trustedmcp.io/badge/remotify-mcp.svg)](https://trustedmcp.io/servers/remotify-mcp)

HTML

<a href="https://trustedmcp.io/servers/remotify-mcp"><img src="https://trustedmcp.io/badge/remotify-mcp.svg" alt="TrustedMCP grade C" height="80"></a>

Community reviews

Keiko Mori Software engineer, agency
Trusts in production Recommends

Exactly what I needed from Remotify

Replaced a homegrown script with Remotify MCP and have not looked back. Releases come often and the changelog is clear. Self-hosting it was straightforward and I like keeping the data on our side. Happy to run it in production.

Used for Scripting routine maintenance tasks

  • Setup & docs 4/5
  • Auth experience 4/5
  • Reliability 3/5
  • Maintainer responsiveness 3/5
Jakub Nowak ML engineer
Trusts with caveats Recommends

Better than the DIY script it replaced

Been running this for about a month now. The auth model is unusual, so I treat the credential like a password and rotate it. Worth it, just do not skip the hardening steps.

Used for Code review summaries for pull requests

  • Setup & docs 4/5
  • Auth experience 5/5
  • Reliability 3/5
  • Maintainer responsiveness 4/5
Vikram Iyer CTO, early-stage startup
Would not trust in production

Does the job, docs could be better

Took longer to configure than I expected. The Docker image made setup trivial and keeps it isolated. Keeping it to local experiments for now.

Used for Keeping project tickets in sync with code changes

  • Setup & docs 2/5
  • Auth experience 3/5
  • Reliability 3/5
  • Maintainer responsiveness 4/5
Karan Mehta Staff engineer
Would not trust in production

Security story needs work

Setup was rough and the result was flaky. Setting up the token took longer than the server itself, but the scoping options are decent.

Used for Automating release notes

  • Setup & docs 1/5
  • Auth experience 3/5
  • Reliability 2/5
  • Maintainer responsiveness 4/5
Maya Johnson Solo founder
Trusts in production Recommends

Surprisingly polished

Our agents call this dozens of times a day. Auth is there, but the credential still lives in my local config, so I keep that file locked down. It is in our production agent and I sleep fine.

Used for Generating boilerplate from existing patterns

  • Setup & docs 5/5
  • Auth experience 5/5
  • Reliability 5/5
  • Maintainer responsiveness 5/5
Omar Haddad Full-stack developer
Trusts with caveats Recommends

Handy for dev, careful in prod

Mostly reliable, with the odd timeout. Updates land regularly, and nothing broke when I upgraded. Self-hosting it was straightforward and I like keeping the data on our side. Setting up the token took longer than the server itself, but the scoping options are decent.

Used for Automating release notes

  • Setup & docs 3/5
  • Auth experience 3/5
  • Reliability 4/5
  • Maintainer responsiveness 4/5
Chris Turner Platform engineer
Trusts in production Recommends

Our team uses it every day

Set this up for our team after comparing a few options. The Docker image made setup trivial and keeps it isolated. Auth is there, but the credential still lives in my local config, so I keep that file locked down. Easy recommendation.

Used for Keeping project tickets in sync with code changes

  • Setup & docs 5/5
  • Auth experience 3/5
  • Reliability 5/5
  • Maintainer responsiveness 5/5
Fatima Zahra Freelance developer
Trusts in production Recommends

The Remotify integration I wanted

Installed it on a Friday, it was part of my workflow by Monday. Took me a minute to understand how auth works here, the note on the listing explains it better than the README. Running it in Docker keeps it away from the rest of my machine.

Used for Pairing with Claude Code on a monorepo

  • Setup & docs 4/5
  • Auth experience 4/5
  • Reliability 4/5
  • Maintainer responsiveness 4/5
Sofia Rossi Eng lead, fintech
Trusts with caveats Recommends

Fine once configured properly

Works well enough for what I need. Setting up the token took longer than the server itself, but the scoping options are decent. You can tell it is actively maintained, the rough edges keep getting fixed. Recommended, with sensible guardrails.

Used for Onboarding new devs with an agent that answers repo questions

  • Setup & docs 3/5
  • Auth experience 2/5
  • Reliability 3/5
  • Maintainer responsiveness 5/5
Mei Lin Backend engineer
Would not trust in production

Would not run this unattended

It works in a demo, but things got shaky under real use. The Docker image made setup trivial and keeps it isolated. You create a token and pass it in. Scope it narrowly, that is the main thing. Keeping it to local experiments for now.

Used for Onboarding new devs with an agent that answers repo questions

  • Setup & docs 2/5
  • Auth experience 3/5
  • Reliability 2/5
  • Maintainer responsiveness 2/5
Hugo Lefevre Security engineer
Would not trust in production

Too many sharp edges

Ran into problems pretty quickly. You create a token and pass it in. Scope it narrowly, that is the main thing. Not something I would put in production yet.

Used for CI failure investigation

  • Setup & docs 2/5
  • Auth experience 3/5
  • Reliability 3/5
  • Maintainer responsiveness 3/5
Tomas Novak AI engineer
Would not trust in production

Mixed feelings after two weeks

Useful tool, though I would not hand it to a junior unsupervised. Took me a minute to understand how auth works here, the note on the listing explains it better than the README.

Used for Letting a coding agent open and triage issues

  • Setup & docs 3/5
  • Auth experience 2/5
  • Reliability 3/5
  • Maintainer responsiveness 3/5
Chloe Martin Indie hacker
Trusts with caveats Recommends

Works, just lock it down

Some tools are great, a couple feel half finished. Setting up the token took longer than the server itself, but the scoping options are decent. Keep permissions tight and it is a good tool.

Used for Debugging sessions in Cursor

  • Setup & docs 3/5
  • Auth experience 2/5
  • Reliability 3/5
  • Maintainer responsiveness 5/5
Tess Murphy CTO, early-stage startup
Would not trust in production

OK for read-only work

It does the job, but it took some tweaking. Read the auth note before you share access with anyone. Once I understood the model I was comfortable with it. You can tell it is actively maintained, the rough edges keep getting fixed.

Used for Generating boilerplate from existing patterns

  • Setup & docs 4/5
  • Auth experience 4/5
  • Reliability 3/5
  • Maintainer responsiveness 4/5
Amara Okeke Senior developer
Trusts with caveats Recommends

Earned a permanent spot in my config

Started with it as an experiment, now it is a fixture. You can tell it is actively maintained, the rough edges keep getting fixed. The auth model is unusual, so I treat the credential like a password and rotate it. I would use it in prod, but only with a human approving writes.

Used for Looking up Remotify data without leaving the editor

  • Setup & docs 3/5
  • Auth experience 4/5
  • Reliability 4/5
  • Maintainer responsiveness 4/5
Ethan Walker Senior developer
Trusts in production Recommends

Recommended it to two teams already

I use this almost daily. Local stdio process, easy to start and stop from the client. Read the auth note before you share access with anyone. Once I understood the model I was comfortable with it. Would recommend without hesitation.

Used for Looking up Remotify data without leaving the editor

  • Setup & docs 4/5
  • Auth experience 4/5
  • Reliability 4/5
  • Maintainer responsiveness 3/5
Isabel Costa Indie hacker
Would not trust in production

Good, but read the permissions first

I like it, with reservations. Running it in Docker keeps it away from the rest of my machine. The auth model is unusual, so I treat the credential like a password and rotate it. Updates land regularly, and nothing broke when I upgraded. Not something I would put in production yet.

Used for Scripting routine maintenance tasks

  • Setup & docs 3/5
  • Auth experience 3/5
  • Reliability 3/5
  • Maintainer responsiveness 4/5
Sam Rivera Developer, healthtech
Would not trust in production

Too much access for my comfort

Gave it a fair shot over two weeks. Releases come often and the changelog is clear. You create a token and pass it in. Scope it narrowly, that is the main thing. I will check back in a few releases.

Used for Internal developer assistant

  • Setup & docs 1/5
  • Auth experience 3/5
  • Reliability 3/5
  • Maintainer responsiveness 3/5
Raj Malhotra Staff engineer
Would not trust in production

Went back to calling the API directly

I wanted to like this one. The Docker image made setup trivial and keeps it isolated. Read the auth note before you share access with anyone. Once I understood the model I was comfortable with it. Updates land regularly, and nothing broke when I upgraded.

Used for Code review summaries for pull requests

  • Setup & docs 1/5
  • Auth experience 3/5
  • Reliability 2/5
  • Maintainer responsiveness 4/5
Samir Khan Eng lead, fintech
Would not trust in production

Fine for a demo, not for prod

Not what I expected from the description. You create a token and pass it in. Scope it narrowly, that is the main thing. For anything real I would look elsewhere.

Used for Letting a coding agent open and triage issues

  • Setup & docs 3/5
  • Auth experience 3/5
  • Reliability 3/5
  • Maintainer responsiveness 4/5

Write a review

Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.

How was it overall?

Would you trust it in production?
Would you recommend it to another team?

Score the details

Setup & docs
Auth experience
Reliability
Maintainer responsiveness

Tell other teams how it went

About you