MCP servers › dev.rent › rent
MCP server · registry snapshot 2026-11-12 · last tested 2026-11-12
rent MCP server
Registry name dev.rent/rent
rent.dev — the publisher's title
by rent.dev · domain (the registry's namespace rule)npm ↗Website ↗
Linux sandboxes billed by the second from a prepaid balance, and GPU pods on your own RunPod key. — the publisher's description
Summary
dev.rent/rent is a remote and local MCP server listed in the official MCP registry at version 0.1.1, under the namespace of the domain rent.dev. On 2026-11-12 ProtocolProbe connected to it in read-only mode and read its inventory: 35 tools, 0 resources and 0 prompts.
Record checks
3 of 6 record checks met · 3 do not apply
- met: Registry entry is active and says how to run it
- not met: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- not met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- not met: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- #11,354 of 20,610 packages by monthly downloads, tied with 17 others
- Not ranked by stars: no public GitHub repository
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- remote and local package
- Transport
- standard input/output, streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Package
- npm · listed version current
- Dependencies
- no known high or critical advisories
- Tools
- 35
- Last tested
- 2026-11-12
Tool list size
17,947 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (35 tools). Counted with Anthropic's token counter on 2026-11-12, from the tool list we read on 2026-11-12. Median across 28,560 counted servers: 2,657 tokens. How it is counted
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-11-12 (mcp.rent.dev), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (0.1.1).
Observed fact
This server accepted a session without any credential and lists 11 tools whose name or declaration suggests they change data (rent_create_sandbox, rent_exec, rent_start_process, rent_run_code, rent_write_file and 6 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-12.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-11-12
- Mode
- read-only (no tool calls)
- Latest version
- 0.1.1, published 2026-11-12 (registry, as of the 2026-11-12 snapshot)
- First listed version
- 2026-11-11 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 2 versions listed, 2026-11-11 to 2026-11-12; 2 in the 90 days before the 2026-11-12 snapshot.(versions still listed in the registry only)
Most recent 2 versions
0.1.1· 2026-11-120.1.0· 2026-11-11
- Registry data
- snapshot 2026-11-12
- Package and repository
- checked 2026-11-12
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn. Does not apply: repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
New in the registry: not in the list of 2026-11-09, listed on 2026-11-12 with version 0.1.1 (published 2026-11-12).
Source: the official MCP Registry list on 2026-11-09 and on 2026-11-12.
What it is
What does this server offer?
Observed inventoryNone of its 35 tools are described as changing anything. For 35 the reading was uncertain, so no mark is shown.
- rent_quote
“Dollars per completed task for rent.dev's own sandboxes beside every published-rate vendor, by workload profile, plus hourly GPU rows.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
profilestring“One profile; default all three.”cpu_countinteger“Default 2.”memory_mbinteger“Default 4096.”
- rent_list_providers
“Lists rent.dev's provider catalog as compact summaries: each provider's capabilities (offerings, pricing types, interfaces, auth and product capabilities), display-only `summary_verdict`, `agentic` f…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
16 inputs
providerstring“One provider id, e.g.”capabilitystring“A capability the provider or one of its products lists, e.g.”usestring“The use the answer asserts: only providers permitting it are listed and only figures whose `publish_mask` allows it are shown.”agentic_onlyboolean“True keeps only providers with a product passing the three-test agentic conjunction.”gpustring“Canonical GPU model id (`h100-sxm-80gb`) or the vendor's own label.”cpustring“The CPU capacity class (`shared`, `dedicated`) or the vendor's product label for a CPU offering (e.g.”architecturestring“Keep CPU offerings whose architecture the vendor states as this value.”coversstring“Keep offerings whose figure covers this unit: `gpu` one GPU, `node`/`instance` a whole node or instance, `gpu_line_item` a fractional GPU line.”figurestring“Keep offerings whose figure was produced this way (`listed`, `floor`, …).”gpu_countinteger“Keep GPU offerings whose `gpu.count` (GPUs per priced unit) is exactly this many; `gpu_count=1` asks for single-GPU offers only.”comparison_groupstring“Keep offerings in exactly this comparison group; `cheapest_offering.comparison_group` names it, and the group's other offers are its comparable peers.”regionstring“A region label or a canonical region id (`us-east-1`), matched without regard to case; either spelling finds every offer in that place.”max_usd_per_hournumber“Keep offerings whose hourly figure (`usd_per_gpu_hour` on a GPU row, else `usd_per_hour`) is at most this many USD.”max_usd_per_vcpu_hournumber“Keep CPU offerings whose `usd_per_vcpu_hour` is at most this many USD.”include_offeringsboolean“True carries every matching offering of the listed providers, not just the cheapest.”limitinteger“Most providers to list, 1-200.”
- rent_search_docs
“Keyword search over the sections of rent.dev's full docs (llms-full.txt): each hit is one section, best first, with its heading path and Markdown.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
querystringrequired“Words to look for, e.g.”limitinteger“Sections to answer.”
- rent_signup
“Creates a rent.dev account and answers its API key, shown this once (store it; it stays valid until revoked), with the MCP URL and the Authorization header that unlocks its account tools, and a three…”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
2 inputs
idempotency_keystring“A random value you choose and keep, such as a UUID, so the signup can be repeated without making a second account.”clientstring“Your MCP client, so that `reconnect` is its own block: claude, claude-ai, codex, cursor, vscode, copilot, gemini, windsurf, cline, zed, opencode, goose, qwen, …”
- rent_supply_guide
“For someone who runs a machine, their own or a VPS rented elsewhere, and wants to sell its compute; to get a machine to use, call rent_create_sandbox instead.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- rent_get_balance
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- rent_topup
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
2 inputs, 2 required
methodstringrequiredamount_usdstringrequired“Credits in USD, e.g.”
- rent_create_sandbox
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
11 inputs
templatestring“Template alias: your own or the public set (`base`, `code-interpreter-v1` for rent_run_code).”timeout_sinteger“Seconds until the sandbox stops (or pauses with auto_pause).”metadataobject“Your labels.”env_varsobject“Environment variables of every command in the sandbox.”auto_pauseboolean“Pause instead of stopping at the timeout.”auto_resumeboolean“Resume a paused sandbox when traffic arrives.”allow_internet_accessbooleannetworkobject“Egress allow and deny lists (CIDR, IP or `*.domain`), and port-URL access.”profilestring“Expected duty, used for placement when there is no history.”routingobject“Endpoint ids to consider besides own supply (a BYOK endpoint needs your stored credential), to avoid, a cold-start bound, and the partner nodes to consider.”wait_sinteger“Seconds to wait for placement before answering with an operation instead.”
- rent_get_sandbox
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
sandbox_idstringrequired“Sandbox id (`lse_…`) from rent_create_sandbox or rent_list_sandboxes.”
- rent_list_sandboxes
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
statestringlimitinteger“Page size, 1-200.”cursorstring
- rent_exec
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
7 inputs, 2 required
sandbox_idstringrequired“Sandbox id (`lse_…`) from rent_create_sandbox or rent_list_sandboxes.”cmdstringrequired“Shell command.”cwdstringenvobjectuserstring“Default `user`.”stdinstring“Written to stdin, then closed.”timeout_sinteger“Seconds before the command is killed.”
- rent_start_process
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
6 inputs, 2 required
sandbox_idstringrequired“Sandbox id (`lse_…`) from rent_create_sandbox or rent_list_sandboxes.”cmdstringrequiredcwdstringenvobjectuserstringstdinboolean“Keep stdin open.”
Show 23 more tools
- rent_get_process_output
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs, 2 required
sandbox_idstringrequired“Sandbox id (`lse_…`) from rent_create_sandbox or rent_list_sandboxes.”process_idstringrequired“From rent_start_process.”cursorstringwait_msinteger“Wait up to this long for new output.”
- rent_run_code
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
6 inputs, 2 required
sandbox_idstringrequired“Sandbox id (`lse_…`) from rent_create_sandbox or rent_list_sandboxes.”codestringrequiredlanguagestring“Default python.”context_idstringenvobjecttimeout_sinteger
- rent_read_file
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 2 required
sandbox_idstringrequired“Sandbox id (`lse_…`) from rent_create_sandbox or rent_list_sandboxes.”pathstringrequired“Absolute path, e.g.”encodingstring
- rent_write_file
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
4 inputs, 3 required
sandbox_idstringrequired“Sandbox id (`lse_…`) from rent_create_sandbox or rent_list_sandboxes.”pathstringrequiredcontentstringrequiredencodingstring
- rent_get_port_url
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 2 required
sandbox_idstringrequired“Sandbox id (`lse_…`) from rent_create_sandbox or rent_list_sandboxes.”portintegerrequired
- rent_extend_sandbox
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
2 inputs, 2 required
sandbox_idstringrequired“Sandbox id (`lse_…`) from rent_create_sandbox or rent_list_sandboxes.”timeout_sintegerrequired
- rent_pause_sandbox
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
1 input, 1 required
sandbox_idstringrequired“Sandbox id (`lse_…`) from rent_create_sandbox or rent_list_sandboxes.”
- rent_resume_sandbox
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
sandbox_idstringrequired“Sandbox id (`lse_…`) from rent_create_sandbox or rent_list_sandboxes.”timeout_sinteger
- rent_terminate_sandbox
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
1 input, 1 required
sandbox_idstringrequired“Sandbox id (`lse_…`) from rent_create_sandbox or rent_list_sandboxes.”
- rent_create_gpu_pod
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
9 inputs, 2 required
gpu_typestringrequired“RunPod GPU type id, e.g.”gpu_countinteger“Default 1.”imagestringrequired“Container image.”cloud_typestring“Default SECURE.”container_disk_gbinteger“Default 20.”volume_gbinteger“Default 0.”portsarray“e.g.”envobjectcredential_idstring“RunPod credential (`cred_…`); default the account's only one.”
- rent_list_gpu_pods
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs
limitinteger“Page size, 1-200.”cursorstring
- rent_terminate_gpu_pod
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
1 input, 1 required
pod_idstringrequired“GPU pod id (`lse_…`) from rent_create_gpu_pod or rent_list_gpu_pods; valid until the pod is terminated, and listed after with its final state.”
- rent_set_byok_credential
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
3 inputs, 2 required
vendorstringrequiredlabelstringfieldsobjectrequired“The vendor's secret fields.”
- rent_get_usage
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs
fromstring“RFC 3339 start.”tostring“RFC 3339 end.”
- rent_get_operation
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
operation_idstringrequired
- rent_supply_enroll
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
6 inputs, 4 required
wirestringrequired“`e2b`: a Linux host where the node kit installs the sandbox stack.”regionstringrequired“A generic region label such as `us-central` or `eu-central`, never a vendor's.”askobjectrequired“What you ask per hour.”capacityobjectrequired“What each node offers.”countinteger“Nodes to enrol: one claim token each.”payoutobject“Where this node's payouts go.”
- rent_supply_nodes
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
limitinteger“Page size, 1-200.”cursorstring
- rent_supply_node
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
node_idstringrequired“Node id (`n` and 15 characters) from rent_supply_nodes, or from the node kit once a node is claimed.”
- rent_supply_update_node
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
6 inputs, 1 required
node_idstringrequired“Node id (`n` and 15 characters) from rent_supply_nodes, or from the node kit once a node is claimed.”askobject“USD per vCPU-hour and per GiB-hour, as decimal strings.”capacityobjectregionstring“A generic label such as `us-central`.”payoutobject“Where this node's payouts go.”signed_nonceobject“Required with `payout`.”
- rent_supply_probe_node
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
1 input, 1 required
node_idstringrequired“Node id (`n` and 15 characters) from rent_supply_nodes, or from the node kit once a node is claimed.”
- rent_supply_revoke_node
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
1 input, 1 required
node_idstringrequired“Node id (`n` and 15 characters) from rent_supply_nodes, or from the node kit once a node is claimed.”
- rent_supply_earnings
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
limitinteger“Entries per page, 1-200.”cursorstring
- rent_supply_payouts
“Needs a rent.dev account: sign in when your client offers it, or call rent_signup first.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
limitinteger“Payouts per page, 1-200.”cursorstringnodestring“Only this node's payouts: its id (`n` and 15 characters) from rent_supply_nodes.”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-12.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 74% of 118
- Tools with a description
- 100% of 35
- Typical description length
- 577 characters
The tool set
Counted from the listing
- Tools
- 35
- Size of the list
- about 45,625 tokens for an agent to load (characters ÷ 4)
- Naming
- 35 of 35 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 35 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the npm package rentdev
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.
Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
"mcpServers": {
"rent": {
"command": "npx",
"args": [
"-y",
"rentdev@0.1.1",
"mcp",
"--stdio"
]
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"rent": {
"command": "npx",
"args": [
"-y",
"rentdev@0.1.1",
"mcp",
"--stdio"
]
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"rent": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"rentdev@0.1.1",
"mcp",
"--stdio"
]
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"rent","type":"stdio","command":"npx","args":["-y","rentdev@0.1.1","mcp","--stdio"]}'Claude Code
claude mcp add --transport stdio rent -- npx -y rentdev@0.1.1 mcp --stdio
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"rent": {
"command": "npx",
"args": [
"-y",
"rentdev@0.1.1",
"mcp",
"--stdio"
],
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"rent": {
"command": "npx",
"args": [
"-y",
"rentdev@0.1.1",
"mcp",
"--stdio"
]
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.rent] command = "npx" args = ["-y", "rentdev@0.1.1", "mcp", "--stdio"]
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"rent": {
"command": "npx",
"args": [
"-y",
"rentdev@0.1.1",
"mcp",
"--stdio"
]
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y rentdev@0.1.1 mcp --stdio
- Arguments are written as the registry entry gives them; a named one as “--name value”, the form the registry documentation shows.
- Optional settings the entry also lists (left out above): RENT_API_KEY.
- This runs the publisher's code on your machine (npx). Read its README first.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-11-12 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://mcp.rent.dev/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"rent": {
"url": "https://mcp.rent.dev/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"rent": {
"type": "http",
"url": "https://mcp.rent.dev/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"rent","type":"http","url":"https://mcp.rent.dev/mcp"}'Claude Code
claude mcp add --transport http rent https://mcp.rent.dev/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"rent": {
"type": "streamableHttp",
"url": "https://mcp.rent.dev/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"rent": {
"httpUrl": "https://mcp.rent.dev/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.rent] url = "https://mcp.rent.dev/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"rent": {
"url": "https://mcp.rent.dev/mcp"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.rent.dev/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 0.1.1
- Latest stable
- 0.1.1
- Status
- current
- Withdrawn
- no
Source: registry.npmjs.org · 2026-11-12. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-11-12 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha512-gzharc//fboqUV4Wf…
- Signature
- signed
Source: the package registry · 2026-11-12.
Usage
- Downloads
- 323 in the last month
Source: api.npmjs.org · 2026-11-12.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- Install-time script (npm). No install-time script in the published package.json (version 0.1.1). Source: registry.npmjs.org/rentdev/0.1.1 · read 2026-11-12.
- Operating systems and processors (npm). The npm package sets no os or cpu limit (package.json). Source: registry.npmjs.org/rentdev/0.1.1 · read 2026-11-12.
- Node.js version (npm). Needs Node 22 or later (engines.node
>=22). Source: registry.npmjs.org/rentdev/0.1.1 · read 2026-11-12. - MCP SDK in the package files. Ships no MCP SDK code in its own files by our rule, and does not list
@modelcontextprotocol/sdkor any of the MCP SDK's split packages (core, server, client, node, express, hono, fastify, server-legacy) as a dependency. Source: registry.npmjs.org/rentdev/-/rentdev-0.1.1.tgz · read 2026-11-12. - Build workflow. No build provenance published for this version. Source: registry.npmjs.org/rentdev/0.1.1 · read 2026-11-12.
Registry entry
- Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-12.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-12. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-12. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-12. Source: read 2026-11-12.
- Cline marketplace. Not in the Cline marketplace on 2026-11-12. Source: read 2026-11-12.
Own host
- security.txt. No security.txt at https://mcp.rent.dev/.well-known/ (HTTP 404, 2026-11-12). No security.txt at https://rent.dev/.well-known/ (HTTP 404, 2026-11-12). Source: mcp.rent.dev/.well-known/security.txt · read 2026-11-12.
- A2A agent card. No A2A agent card at https://mcp.rent.dev/.well-known/ (HTTP 404, 2026-11-12). No A2A agent card at https://rent.dev/.well-known/ (HTTP 404, 2026-11-12). Source: mcp.rent.dev/.well-known/agent-card.json · read 2026-11-12.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint mcp.rent.dev/mcp | Session opened | matches | our test · 2026-11-12 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-11-12 |
| Version 0.1.1 on npm | Exists and can be installed | matches | npm · 2026-11-12 |
Choosing
Record checks
Public records · not a safety rating3 of 6 record checks met · 3 do not apply
- #11,354 of 20,610 packages by monthly downloads, tied with 17 others
- Not ranked by stars: no public GitHub repository
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- Not metPackage names its licence with a standard (SPDX) identifierA licence is mentioned, but not as a standard identifier (for example "SEE LICENSE IN …").What changes this check: For an npm package, the documentation describes naming the licence in the license field of package.json with a current SPDX license identifier. npm: package.json license field
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
- Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.What changes this check: npm's documentation describes publishing with provenance from a cloud-hosted runner of a supported CI/CD provider, using npm CLI 9.5.0 or newer and npm publish --provenance. npm: generating provenance statements
- MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-12. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about dev.rent/rent
Answered from the data aboveWho publishes dev.rent/rent?
The registry ties the namespace dev.rent to the domain rent.dev; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.
Is dev.rent/rent safe to install?
We do not rate servers as safe or unsafe. 3 of its 6 applicable record checks are met (facts from public records, each listed on this page). What the records show: The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Does dev.rent/rent need an API key or sign-in?
It opened a session without any credential on 2026-11-12. The registry entry declares no required credential; no declaration is not a guarantee.
Has dev.rent/rent been security tested?
Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.
Is the listed version current?
Yes. The registry lists 0.1.1, the latest stable release on npm.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Open without sign-in
It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: exercised
3 exercised12 not run (reason given)3 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
Source: our own test, 2026-11-12, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 1,722 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 35 tools, 0 resources, 0 prompts.
- 3,260 msFinished: 3 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “dev.rent/rent: MCP server record.” Data checked 2026-11-12. https://protocolprobe.com/mcp/servers/dev.rent/rent
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/dev.rent/rent)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology