Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.digitalimpresys/rentme-tasks

REMOTE · EFFICIENT-PERFECTION-PRODUCTION-EDBC.UP.RAILWAY.APP · SCANNED SEP 28

AI Requests for physical tasks performed by humans registered on Rentme, in exchange for payment.

+3 this week 69 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 514 tokens (~171/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.digitalimpresys/rentme-tasks MCP server?

io.github.digitalimpresys/rentme-tasks is a hosted endpoint at https://efficient-perfection-production-edbc.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · efficient-perfection-production-edbc.up.railway.app

# add to Claude Code
claude mcp add --transport http digitalimpresys-rentme-tasks 'https://efficient-perfection-production-edbc.up.railway.app/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "digitalimpresys-rentme-tasks": {
      "url": "https://efficient-perfection-production-edbc.up.railway.app/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "digitalimpresys-rentme-tasks": {
      "type": "http",
      "url": "https://efficient-perfection-production-edbc.up.railway.app/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.digitalimpresys-rentme-tasks]
url = "https://efficient-perfection-production-edbc.up.railway.app/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "digitalimpresys-rentme-tasks": {
      "type": "remote",
      "url": "https://efficient-perfection-production-edbc.up.railway.app/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add digitalimpresys-rentme-tasks --url 'https://efficient-perfection-production-edbc.up.railway.app/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  digitalimpresys-rentme-tasks:
    url: "https://efficient-perfection-production-edbc.up.railway.app/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "digitalimpresys-rentme-tasks": {
      "Transport": "http",
      "Url": "https://efficient-perfection-production-edbc.up.railway.app/mcp"
    }
  }
}
# add to Vellum
assistant mcp add digitalimpresys-rentme-tasks -t streamable-http -u 'https://efficient-perfection-production-edbc.up.railway.app/mcp'
// mcp.json
{
  "mcpServers": {
    "digitalimpresys-rentme-tasks": {
      "type": "http",
      "url": "https://efficient-perfection-production-edbc.up.railway.app/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Sept 26 0
    • Schema quality: 152 → 171 ▼ functional
    • Server version: 1.0.2 → 1.0.3 functional
    • “rentme_create_task” added an optional parameter “posti_totali” cosmetic
  • 20 Sept 26 0
    • Server version: 1.0.1 → 1.0.2 functional
    • “rentme_create_task” added an optional parameter “webhook_url” cosmetic
  • 19 Sept 26 +1
    • Tool “rentme_create_task” rewrote its description, which is the text the model reads security
    • Schema quality: 310 → 420 ▼ functional
    • Server version: 1.0.0 → 1.0.1 functional
    • New tool “rentme_list_skills” functional
    • “rentme_create_task” added an optional parameter “skill_id” cosmetic
  • 18 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 28 Sept 2026 · Probed https://efficient-perfection-production-edbc.up.railway.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.up.railway.app CN=YE2,O=Let's Encrypt,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA384 618edc56941aa1165ddb080bf9f799eb7c1
SANs: *.up.railway.app, up.railway.app
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of efficient-perfection-production-edbc.up.railway.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
railway.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://efficient-perfection-production-edbc.up.railway.app/mcp Verified 200
http (plaintext) http://efficient-perfection-production-edbc.up.railway.app/mcp HTTPS enforced 301 https://efficient-perfection-production-edbc.up.railway.app/mcp
MCP tools · 3 exposed · ~514 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
rentme_check_task_status ~93

Controlla lo stato di avanzamento di un task creato su Rentme (aperto, assegnato, in_corso, completato, annullato), cercandolo per id interno o per riferimento_ai fornito in fase di creazione.

NameTypeReqDescription
idinteger–ID interno del task
riferimento_aistring–Riferimento esterno fornito alla creazione

No output schema declared.

No examples provided.

rentme_create_task ~357

Pubblica una richiesta di operazione fisica nel mondo reale (sopralluogo, consegna, verifica, montaggio, ecc.) sulla bacheca Rentme, dove collaboratori umani registrati possono candidarsi per eseguirla dietro compenso. Usa questo strumento quando serve far compiere un'azione fisica reale da una persona. Se vuoi associare una competenza specifica, chiama prima rentme_list_skills per conoscere gli id disponibili.

NameTypeReqDescription
compensonumberyesCompenso offerto, nella valuta indicata
descrizionestringyesDescrizione dettagliata di cosa va fatto
luogo_testualestring–Luogo in cui va svolto il task
posti_totaliinteger–Quante persone possono essere assegnate a questo stesso task prima che sparisca dalla bacheca (default 1). Utile per richieste ripetibili, es. "condividi un post" valida per 100 persone.
riferimento_aistring–Riferimento a piacere per ritrovare il task in seguito con rentme_check_task_status
scadenzastring–Scadenza, formato "YYYY-MM-DD HH:MM:SS"
skill_idinteger–ID della competenza richiesta, ottenuto da rentme_list_skills
titolostringyesTitolo breve del task
valutastring–Codice valuta a 3 lettere, es. EUR
webhook_urlstring–URL https:// a cui Rentme invierà una notifica automatica quando lo stato del task cambia (es. quando viene completato)

No output schema declared.

No examples provided.

rentme_list_skills ~64

Ritorna il catalogo delle competenze (skill) disponibili su Rentme, con il loro id. Usa questo strumento PRIMA di rentme_create_task quando vuoi associare una competenza specifica al task, per sapere quale skill_id passare.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the io.github.digitalimpresys/rentme-tasks MCP server?

io.github.digitalimpresys/rentme-tasks is an MCP server listed in the public MCP registry as io.github.digitalimpresys/rentme-tasks. AI Requests for physical tasks performed by humans registered on Rentme, in exchange for payment. This page covers its hosted endpoint (https://efficient-perfection-production-edbc.up.railway.app/mcp).

Is the io.github.digitalimpresys/rentme-tasks MCP server safe to use?

io.github.digitalimpresys/rentme-tasks scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.digitalimpresys/rentme-tasks MCP server expose?

io.github.digitalimpresys/rentme-tasks exposes 3 tools: rentme_list_skills, rentme_create_task, rentme_check_task_status. Their descriptions and schemas cost roughly 514 tokens of context every time the server is loaded.

Does the io.github.digitalimpresys/rentme-tasks MCP server require authentication?

No. We connected to io.github.digitalimpresys/rentme-tasks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.digitalimpresys/rentme-tasks MCP server still maintained?

io.github.digitalimpresys/rentme-tasks is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.