Rash

io.github.paimlPublished by GitHub account paimlv0.1.0Updated Oct 24, 2026

Transpile Rust code to POSIX-compliant shell scripts with formal correctness guarantees

VerifiedSTDIODesktop onlyDeveloper Tools

Server details

Identifier: io.github.paiml/rash
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account paiml for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.paiml%2Frash.svg)](https://sourceweft.com/mcp/io.github.paiml%2Frash?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Transpiles Rust code into POSIX-compliant shell scripts with formal correctness guarantees.

What you can do: Rash is a local MCP server that lets an assistant transpile Rust code into POSIX-compliant shell scripts. According to its registry description, it aims to provide formal correctness guarantees for the generated scripts. No individual tools are listed in the manifest, so the exact operations exposed to the assistant are not documented here.
When to use it: Worth considering when you want an assistant to turn Rust logic into portable shell scripts, for example to ship build or deployment steps that must run under a POSIX shell. It is a desktop-only local process, so it suits individual developer machines rather than hosted or browser-based setups.
Requirements: Runs as a local process on the user's machine over stdio, and is marked desktop-only with no web executable. No packages, authentication, environment variables, or headers are declared, so the runtime and any toolchain requirements are not specified in the available information.

Before you install

The manifest declares no credentials, environment variables, or headers, and no tools are listed, so there is no documented indication of what the server reads, writes, or sends. Because generated shell scripts can execute commands on your machine, review any script before running it.

Installation

In SourceWeft

Open Rash in the dashboard and add it to a workspace.
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.

Tools

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

Version history

v0.1.0LatestSep 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.