mcp-registry/io.github.digitalimpresys/rentme-tasks · v1.1.0
As of 2026-10-18 16:47 UTC, the Digitalimpresys Rentme Tasks MCP server is unknown with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 13 minutes.
AI Requests for physical tasks performed by humans registered on Rentme, in exchange for payment.
Point your MCP client at this streamable-http endpoint: https://efficient-perfection-production-edbc.up.railway.app/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
9 of 9 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~1,627 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 2 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.digitalimpresys%2Frentme-tasks/fixes
{
"name": "rentme_book_thing",
"description": "Invia una richiesta di noleggio per conto di una persona. Il proprietario (Runner) ha 24 ore per accettare; quando accetta, la persona riceve per email un link di pagamento con carta da usare entro 12 ore (lo trovi anche in rentme_check_rental_status). Solo dopo il pagamento il noleggio è confermato e si scambiano i contatti. Chiedi sempre conferma alla persona prima di prenotare, mostrando periodo e prezzo totale. Conserva id e codice_accesso restituiti: servono per controllare lo stato o annul",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"thing_id",
"tipo_tariffa",
"data_inizio",
"quantita",
"indirizzo_consegna",
"nome_cliente",
"telefono_cliente",
"email_cliente"
],
"properties": {
"note": {
"type": "string",
"description": "Note per il Runner, es. citofono, piano"
},
"quantita": {
"type": "integer",
"description": "Durata: numero di ore, giorni o mesi secondo tipo_tariffa",
"exclusiveMinimum": 0
},
"thing_id": {
"type": "integer",
"description": "Id dell'oggetto"
},
"data_inizio": {
"type": "string",
"description": "Data e ora di consegna, formato \"YYYY-MM-DD HH:MM\", tra le 07:00 e le 21:00, minuti 00 o 30"
},
"webhook_url": {
"type": "string",
"format": "uri",
"description": "URL https:// per ricevere notifiche automatiche ai cambi di stato"
},
"nome_cliente": {
"type": "string",
"description": "Nome e cognome di chi riceve l'oggetto"
},
"tipo_tariffa": {
"enum": [
"ora",
"giorno",
"mese"
],
"type": "string",
"description": "Tariffa da usare: deve essere tra quelle offerte dall'oggetto"
},
"email_cliente": {
"type": "string",
"format": "email",
"description": "Email di chi noleggia: riceverà link di pagamento e conferme"
},
"riferimento_ai": {
"type": "string",
"description": "Riferimento a piacere per il tuo sistema"
},
"telefono_cliente": {
"type": "string",
"description": "Telefono di chi riceve l'oggetto (lo userà il Runner per la consegna)"
},
"indirizzo_consegna": {
"type": "string",
"description": "Indirizzo completo di consegna: via, numero, CAP, città"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Richiedi il noleggio di un oggetto"
}{
"name": "rentme_cancel_rental",
"description": "Annulla per conto della persona un noleggio richiesto con rentme_book_thing. Gratis prima del pagamento. Dopo il pagamento: fino a 24 ore prima della consegna rimborso meno il 3% di spese (min 1 EUR); a meno di 24 ore nessun rimborso. Chiedi conferma alla persona prima di annullare.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id",
"codice_accesso"
],
"properties": {
"id": {
"type": "integer",
"description": "Id del noleggio"
},
"codice_accesso": {
"type": "string",
"description": "Codice di accesso restituito da rentme_book_thing"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
},
"title": "Annulla un noleggio"
}{
"name": "rentme_check_rental_status",
"description": "Stato di un noleggio richiesto con rentme_book_thing: richiesto (in attesa del Runner), da_pagare (contiene link_pagamento da dare alla persona), confermato (contiene nome e contatto del Runner), consegnato, completato, rifiutato, scaduto, annullato.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id",
"codice_accesso"
],
"properties": {
"id": {
"type": "integer",
"description": "Id del noleggio"
},
"codice_accesso": {
"type": "string",
"description": "Codice di accesso restituito da rentme_book_thing"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Controlla lo stato di un noleggio"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.digitalimpresys/rentme-tasks"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.digitalimpresys/rentme-tasks"}) over MCP.
rentme_book_thing ~565 tokensrentme_create_task ~520 tokensrentme_search_things ~290 tokensrentme_get_thing ~187 tokensrentme_cancel_rental ~181 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.digitalimpresys%2Frentme-tasks?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.digitalimpresys%2Frentme-tasks?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.digitalimpresys%2Frentme-tasks.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.digitalimpresys%2Frentme-tasks.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.digitalimpresys%2Frentme-tasks?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:4fb8172081e81f7a…, first seen 2026-10-17, included at leaf 3856 of 27,217. Version history · verify what your client received.
Compare: most reliable other servers · most reliable retrieval servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 16:47 UTC, the Digitalimpresys Rentme Tasks MCP server is unknown with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 13 minutes.
Digitalimpresys Rentme Tasks MCP server advertises 9 tools, including rentme_book_thing, rentme_cancel_rental, rentme_check_rental_status, rentme_check_task_status, rentme_create_task.
Point your MCP client at this streamable-http endpoint: https://efficient-perfection-production-edbc.up.railway.app/mcp
Glimind scanned all 9 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.