Skip to content

Snapforge Ship-Ready Check MCP server

com.snapforgelab/ship-ready-checksnapforgelab.comstreamable-httpv1.0.0Scanned

Free, read-only ship-readiness check for Replit, Lovable and Bolt apps.

2 tools: 1 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 1 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 1
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Snapforge Ship-Ready Check MCP server can do

The Snapforge Ship-Ready Check MCP server is published by snapforgelab.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: check_app), but cannot delete data. 1 tool only reads.

2 tools bring in text other people can write (check_app and get_fix_prompt); 1 tool can send data out of your system (check_app).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 14, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Changes things 1Claude Code: ask
  • check_appRun a passive, read-only launch check on the public URL of a live app the user owns or is authorized to test (built with Replit, Lovable or Bolt).Reads text others writeCan send data out1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "check_app" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run a passive, read-only launch check on the public URL of a live app the user owns or is authorized to test (built with Replit, Lovable or Bolt). Checks: reachable and fast, SEO title/meta, robots/sitemap, security headers, open CORS, and a dev banner left in production. Only reads what any visitor's browser already sees (homepage, response headers, robots.txt, sitemap.xml); never scans JavaScript bundles for secrets, never signs in, submits forms, writes data or reads databases. Refuse private/internal addresses.

    Annotations the server declares

    • title: Ship-ready check
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • get_fix_promptReturn a paste-ready prompt to fix a specific issue in the user's builder (Replit Agent, Lovable or Bolt).Reads text others writeNo findings

    Why it is in this group

    • The name "get_fix_prompt" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    Return a paste-ready prompt to fix a specific issue in the user's builder (Replit Agent, Lovable or Bolt). Use the issue id from check_app.

    Annotations the server declares

    • title: Get fix prompt
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:47 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.snapforgelab.com/mcp: tools/list returned 2 tools to an anonymous client, including check_app (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "check_app" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The description's first verb is "run": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http ship-ready-check https://mcp.snapforgelab.com/mcp
claude mcp add --transport http ship-ready-check https://mcp.snapforgelab.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ship-ready-check__get_fix_prompt"
    ],
    "ask": [
      "mcp__ship-ready-check__check_app"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ship-ready-check. Review it before you use it.

Capability tags behind 2 rules
  • mcp__ship-ready-check__check_app untrusted-input, outbound
  • mcp__ship-ready-check__get_fix_prompt untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.snapforgelab/ship-ready-check/verify?hash=ff16c77becef07c443cd18f0024bea2860acbba26d626c3c5e44335e77349f48" | jq -e '.changed == false'

Pinned hash ff16c77becef, from Nov 14, 2026, 09:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.snapforgelab/ship-ready-check/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.snapforgelab/ship-ready-check
[![Anlyon Radar](https://radar.anlyon.com/badge/com.snapforgelab/ship-ready-check.svg)](https://radar.anlyon.com/servers/com.snapforgelab/ship-ready-check)

Source: MCP Registry. Synced Oct 21, 2026, 18:05 UTC.

Snapforge Ship-Ready Check MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Snapforge Ship-Ready Check MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Snapforge Ship-Ready Check MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Snapforge Ship-Ready Check MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Snapforge Ship-Ready Check MCP server have?

2 tools: 1 write, 1 read. check_app and get_fix_prompt.

Does the Snapforge Ship-Ready Check MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Snapforge Ship-Ready Check MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_app.

Has the Snapforge Ship-Ready Check MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.