Skip to main content
Glama

slipway

crates.io MCP Registry

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.

Related MCP server: mobile-debug-mcp

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      MCP server for offline verification of signed artifacts — receipts, manifests, and audit bundles. MIT licensed, works without accounts or API calls. Tools: self_test, verify_receipt, verify_bundle, explain_artifact.
      4
      6
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      A sovereign, MIT-licensed MCP server for professional-service workflows, providing offline-capable, Ed25519-signed tools for autonomous agents and human developers.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A local-first, model-neutral MCP server for collecting and normalizing change-scoped release evidence. It provides deterministic Git change summaries, evidence collection, and review bundles for agent review.
      7
      4 npm
      Apache 2.0