Rentme Tasks

io.github.digitalimpresysPublished by GitHub account digitalimpresysv1.0.1Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Lets an assistant post paid requests for physical tasks to be performed by human workers registered on Rentme.

What you can do
This remote MCP server connects an assistant to Rentme, a marketplace where physical tasks are carried out by human workers. According to the registry description, it handles AI requests for physical tasks performed by humans in exchange for payment. No tool list is published, so the exact operations available are not documented here.
When to use it
Consider it when an assistant needs to delegate a real-world, physical errand to a person rather than complete it digitally, and when paying for that work is acceptable. It is not useful for tasks that can be finished entirely in software.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's hosted address. No packages, environment variables, headers, or authentication are declared in the manifest, and no account or credential setup is described.
Before you install
The server involves payment for work performed by humans, so requests may incur real costs; spending limits and approval steps are not described. The manifest declares no authentication, so anyone reaching the endpoint may be able to submit requests. Task details are sent to a third-party marketplace and its workers.

Installation

In SourceWeft

  1. Open Rentme Tasks in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.digitalimpresys%2Frentme-tasks/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.1LatestSep 18, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.