# io.github.digitalimpresys/rentme-tasks (remote · efficient-perfection-production-edbc.up.railway.app)

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

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `efficient-perfection-production-edbc.up.railway.app`: 69/100 (this document), [markdown](https://verifymcp.io/servers/digitalimpresys-rentme-tasks/efficient-perfection-production-edbc.md), [page](https://verifymcp.io/servers/digitalimpresys-rentme-tasks/efficient-perfection-production-edbc)

## Channel facts

- Endpoint: `https://efficient-perfection-production-edbc.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http digitalimpresys-rentme-tasks 'https://efficient-perfection-production-edbc.up.railway.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "digitalimpresys-rentme-tasks": {
      "url": "https://efficient-perfection-production-edbc.up.railway.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "digitalimpresys-rentme-tasks": {
      "type": "http",
      "url": "https://efficient-perfection-production-edbc.up.railway.app/mcp"
    }
  }
}
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add digitalimpresys-rentme-tasks --url 'https://efficient-perfection-production-edbc.up.railway.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  digitalimpresys-rentme-tasks:
    url: "https://efficient-perfection-production-edbc.up.railway.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "digitalimpresys-rentme-tasks": {
      "Transport": "http",
      "Url": "https://efficient-perfection-production-edbc.up.railway.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add digitalimpresys-rentme-tasks -t streamable-http -u 'https://efficient-perfection-production-edbc.up.railway.app/mcp'
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 69, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 69, +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.

### 2026-09-25 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-22 (score 67, +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.

### 2026-09-21 (score 66, 0)

- [functional regression] Schema quality: 152 → 171
- [functional] Server version: 1.0.2 → 1.0.3
- [cosmetic] “rentme_create_task” added an optional parameter “posti_totali”

### 2026-09-20 (score 66, 0)

- [functional] Server version: 1.0.1 → 1.0.2
- [cosmetic] “rentme_create_task” added an optional parameter “webhook_url”

### 2026-09-19 (score 66, +1)

- [security] Tool “rentme_create_task” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 310 → 420
- [functional] Server version: 1.0.0 → 1.0.1
- [functional] New tool “rentme_list_skills”
- [cosmetic] “rentme_create_task” added an optional parameter “skill_id”

### 2026-09-18 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (3)

### `rentme_list_skills` (~64 tokens)

Elenca le competenze disponibili su Rentme

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.

### `rentme_create_task` (~357 tokens)

Crea un task su Rentme

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.

Input parameters:

- `compenso` (number, required): Compenso offerto, nella valuta indicata
- `descrizione` (string, required): Descrizione dettagliata di cosa va fatto
- `luogo_testuale` (string): Luogo in cui va svolto il task
- `posti_totali` (integer): 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_ai` (string): Riferimento a piacere per ritrovare il task in seguito con rentme_check_task_status
- `scadenza` (string): Scadenza, formato "YYYY-MM-DD HH:MM:SS"
- `skill_id` (integer): ID della competenza richiesta, ottenuto da rentme_list_skills
- `titolo` (string, required): Titolo breve del task
- `valuta` (string): Codice valuta a 3 lettere, es. EUR
- `webhook_url` (string): URL https:// a cui Rentme invierà una notifica automatica quando lo stato del task cambia (es. quando viene completato)

### `rentme_check_task_status` (~93 tokens)

Controlla lo stato di un task Rentme

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.

Input parameters:

- `id` (integer): ID interno del task
- `riferimento_ai` (string): Riferimento esterno fornito alla creazione

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/digitalimpresys-rentme-tasks/efficient-perfection-production-edbc#diagnostics

## Score history

- 2026-09-28: 69
- 2026-09-27: 69
- 2026-09-26: 68
- 2026-09-25: 68
- 2026-09-24: 67
- 2026-09-23: 67
- 2026-09-22: 67
- 2026-09-21: 66
- 2026-09-20: 66
- 2026-09-19: 66
- 2026-09-18: 65
- 2026-09-17: 65

## 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.

## Links

- Remote endpoint: https://efficient-perfection-production-edbc.up.railway.app/mcp
- Repository: https://github.com/digitalimpresys/rentme-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/digitalimpresys-rentme-tasks/efficient-perfection-production-edbc.xml
- Changelog JSON feed: https://verifymcp.io/servers/digitalimpresys-rentme-tasks/efficient-perfection-production-edbc.json
- HTML version of this page: https://verifymcp.io/servers/digitalimpresys-rentme-tasks/efficient-perfection-production-edbc