Home / MCP registry index / dev.rent/rent

rent.dev

dev.rent/rent in the official MCP registry. Endpoint https://mcp.rent.dev/mcp.

The registry describes it as: Linux sandboxes billed by the second from a prepaid balance, and GPU pods on your own RunPod key.

We read its 35 tools on 2026-11-12. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again about every two weeks.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http rent https://mcp.rent.dev/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "rent": {
      "url": "https://mcp.rent.dev/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"rent","type":"http","url":"https://mcp.rent.dev/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

rent_quote rent_list_providers rent_search_docs rent_signup rent_supply_guide rent_get_balance rent_topup rent_create_sandbox rent_get_sandbox rent_list_sandboxes rent_exec rent_start_process rent_get_process_output rent_run_code rent_read_file rent_write_file rent_get_port_url rent_extend_sandbox rent_pause_sandbox rent_resume_sandbox rent_terminate_sandbox rent_create_gpu_pod rent_list_gpu_pods rent_terminate_gpu_pod rent_set_byok_credential rent_get_usage rent_get_operation rent_supply_enroll rent_supply_nodes rent_supply_node rent_supply_update_node rent_supply_probe_node rent_supply_revoke_node rent_supply_earnings rent_supply_payouts

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-12): e0f1df55c37587da. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/dev-rent-rent/badge.svg)](https://lazaretto.dev/mcp-registry/dev-rent-rent)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.