Slipway

ai.qompassPublished by qompass.aiv1.0.0Updated Nov 3, 2026

Android build/sign/verify/install/release MCP server with measured certification gates.

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

Slipway's local MCP server, published by qompass.ai; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Publisher
qompass.ai

Installation

In SourceWeft

  1. Open Slipway 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

slipway

A small deterministic Rust MCP server that builds, signs, verifies, installs, and prepares releases of the Owner's own Android apps — and nothing else. Slipway never sees reference artifacts: the methodology firewall keeps fathom (which censuses) and slipway (which ships) separate, and the study document is the only bridge (workflow SB-1: study → bridge → build → census-back → conformance diff).

Posture: read-class tools land and gate first; signing is consequential-class, gated by the signed-authority chain from its first day; every action appends to the slipway.receipt log; the release bundle is the deliverable and store submission stays a human act. No build is authorized by the program documents alone — stages run on the Owner's word.

Status — 1.0.0 (2026-10-28)

Version 1.0.0 of the crate slipway-mcp (binary slipway): rmcp 3.8.0, modern MCP protocol era only (2026-07-28), 15 tools in class order — read: slipway_status, slipway_toolchain, slipway_inspect, slipway_verify, slipway_release_check, slipway_certify, slipway_bundle_check; execute: slipway_build, slipway_install, slipway_device_open, slipway_device_verify, slipway_device_close, slipway_drive_app; consequential: slipway_sign, slipway_release. The full from-birth gate record is in BUILD-REPORT.md (S0–S4 PASS; the four D-121 certification verdicts not_certified solely on Owner-side items); the 1.0.0 re-gate and a scripted release-prep utilization session are recorded in UTILIZATION.md and CHANGELOG.md. The Progress tracker below predates the build (it is generated from CHECKLIST.md, which still carries the pre-build checklist); the documents named here are the current record.

Progress

[slipway progress tracker]

7% — 2 of 28 gates closed, 3 delivered and awaiting gate — updated 2026-10-21. Full record: CHECKLIST.md — every item traces to a stage gate in the program documents; the bar moves only on gated evidence.

Progress here is tracked from ideation to the finished 1.0 and beyond: each checklist item is a stage gate from the program documents, and it closes only on verified evidence.

License

Apache-2.0 — see LICENSE.

Source: README.md at commit 0932abc

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

2
  1. v1.0.0LatestNov 3, 2026
  2. v0.1.0Oct 29, 2026

Score

50% 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
  • License10 pts