RecourseOS

io.github.recourseOSPublished by GitHub account recourseOSv0.1.12Updated Oct 24, 2026

Consequence evaluation for AI agents. Check recoverability before destructive actions.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

RecourseOS is a local MCP server that evaluates the consequences of an AI agent's actions, letting an assistant check whether a destructive step is recoverable.

What you can do
Evaluate the consequences of a proposed action before it is carried out, per the registry description of consequence evaluation for AI agents. Check recoverability of a destructive action before proceeding. The manifest lists no tools, so the exact operations available are not documented in the supplied material.
When to use it
Worth considering when an assistant is about to take destructive or hard-to-undo actions and you want a recoverability check first. The supplied material gives no further detail on scope or workflow.
Requirements
Runs as a local process on the user's machine via the npm package recourse-cli over stdio. Desktop only; no web executable. No authentication, environment variables or headers are declared.
Before you install
The server is positioned around destructive actions, so treat its output as advisory rather than a guarantee; the supplied material documents no tools, README or instructions, so behavior cannot be verified before installing. No credentials are declared.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.12LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 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.