Proofsheet

dev.proofsheetPublished by proofsheet.devv0.1.18Updated Nov 6, 2026

Run e2e flows on real iOS and Android phones through the local Proofsheet hub (macOS).

VerifiedSTDIODesktop onlyDeveloper Tools

Server details

Identifier: dev.proofsheet/proofsheet
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Oct 29, 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 that this server's namespace belongs to proofsheet.dev. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

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/dev.proofsheet%2Fproofsheet.svg)](https://sourceweft.com/mcp/dev.proofsheet%2Fproofsheet?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that lets an assistant run end-to-end test flows on real iOS and Android phones through the Proofsheet hub on macOS.

What you can do: Run end-to-end test flows on physical iOS and Android devices via the local Proofsheet hub.
Drive and observe real phones rather than emulators, as part of an assistant-led testing workflow.
The manifest lists no individual tools, so the exact operations available are not documented here.
When to use it: Useful when you want an AI assistant to execute or iterate on mobile end-to-end tests against real iOS or Android hardware, and you already run the Proofsheet hub on a Mac.
Requirements: Runs as a local stdio process, installed from the npm package proofsheet-mcp, on macOS only (desktop only, not web-executable). A local Proofsheet hub and connected physical iOS and Android devices are needed. No authentication, environment variables or headers are declared.

Before you install

It drives real physical devices, so test flows can change app state or data on those phones. The manifest declares no credentials, but the local hub and device connection are outside what is documented here; verify what the hub exposes before use.

Installation

In SourceWeft

Open Proofsheet 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 started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package did not install.

Version history

v0.1.18LatestNov 6, 2026
v0.1.17Nov 5, 2026
v0.1.14Nov 3, 2026
v0.1.13Oct 31, 2026
v0.1.8Oct 29, 2026

Score

15% 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
Publish an icon in the registry entry.
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.