ShipCheck

io.github.wtaylorwilsonPublished by GitHub account wtaylorwilsonv0.1.0Updated Oct 24, 2026

Independent preview-URL QA for coding agents. Playwright heuristics, pass/fail pack.

The publisher's own server: check.tattoo: tattoo size and placement guide

VerifiedStreamable HTTPWeb executableBrowser AutomationDeveloper Tools

Overview

AI-generated overview

ShipCheck is a remote MCP endpoint that gives coding agents independent QA checks on preview URLs, using Playwright-based heuristics with pass/fail results.

What you can do
  • Run QA checks against a preview URL supplied by the assistant.
  • Apply Playwright-based heuristics to the page under test.
  • Return pass/fail results as a pack for the agent to act on.
  • No individual tools are listed in the manifest, so the exact operations are not documented.
When to use it
Useful when a coding agent has produced a preview deployment and you want an independent check of that URL before shipping, rather than relying on the agent's own assessment.
Requirements
A remote streamable HTTP endpoint; nothing to install locally. No authentication, environment variables or headers are declared, so the endpoint is reachable without credentials.
Before you install
The preview URL you submit is sent to a third-party service, so avoid URLs exposing private or internal content. The endpoint is hosted on a temporary-looking tunnel domain and no authentication is declared, so availability and trustworthiness are unverified. Write, send or delete behaviour is not documented.

Installation

In SourceWeft

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

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.wtaylorwilson%2Fshipcheck/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "shipcheck": {
      "type": "http",
      "url": "https://realtor-all-enclosed-altered.trycloudflare.com/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

28% 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 daysRequired25 pts

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

  • Auth declaredRequired10 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Check integrations