MCP servers observed by Lowdown
dev.rent/rent MCP server: daily status and tool changes
Answered initialize and tools/list on the last 2 consecutive checks (2026-11-15 to 2026-11-18) (Lowdown checks this server every 3 days); 35 tools listed. 2 of 3 checks in the last 30 days had this result. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-12; no tool definition change in 1 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.rent/rent
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.rent/rent?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 2
- Required authentication: 1
- No response: 0
- Remotes differed: 0
Does it require authentication?
It returned HTTP 401/403 on 1 of 3 observed days. Lowdown checks without credentials, so the tools behind authentication were not listed.
Did its tools change recently?
No change in tool schemas, descriptions or names across 1 compared days.
What tools does it list?
35 tools on 2026-11-18:
rent_create_gpu_podrent_create_sandboxrent_execrent_extend_sandboxrent_get_balancerent_get_operationrent_get_port_urlrent_get_process_outputrent_get_sandboxrent_get_usagerent_list_gpu_podsrent_list_providersrent_list_sandboxesrent_pause_sandboxrent_quoterent_read_filerent_resume_sandboxrent_run_coderent_search_docsrent_set_byok_credentialrent_signuprent_start_processrent_supply_earningsrent_supply_enrollrent_supply_guiderent_supply_noderent_supply_nodesrent_supply_payoutsrent_supply_probe_noderent_supply_revoke_noderent_supply_update_noderent_terminate_gpu_podrent_terminate_sandboxrent_topuprent_write_file
MCP Registry declaration
- Registry name:
dev.rent/rent - Declared version: 0.1.1
- Status: active
- Declared hosts:
mcp.rent.dev
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:dev.rent/rent", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.rent/rent?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:dev.rent/rent -- npx -y rentdev
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).