# app.goshipyard/shipyard (remote · goshipyard.app)

Ship, discover and review vibe-coded projects on Shipyard, the invite-only feed for AI-built apps.

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `goshipyard.app`: 70/100 (this document), [markdown](https://verifymcp.io/servers/app-goshipyard-shipyard/goshipyard.md), [page](https://verifymcp.io/servers/app-goshipyard-shipyard/goshipyard)

## Channel facts

- Endpoint: `https://goshipyard.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 917 tokens (~101/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http app-goshipyard-shipyard https://goshipyard.app/mcp
```

### Codex

```toml
[mcp_servers.app-goshipyard-shipyard]
url = "https://goshipyard.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-goshipyard-shipyard": {
      "type": "remote",
      "url": "https://goshipyard.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-goshipyard-shipyard --url https://goshipyard.app/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-goshipyard-shipyard:
    url: "https://goshipyard.app/mcp"
```

### Other

```json
{
  "mcpServers": {
    "app-goshipyard-shipyard": {
      "type": "http",
      "url": "https://goshipyard.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 65)

First indexed and scored.

## MCP tools (9)

### `list_projects` (~136 tokens)

List / search projects

Browse or search the Shipyard feed. Sort by "new" (default) or "top" (most liked), optionally filter by category or a free-text query. Set mine=true to list only your own projects (needs an API key).

Input parameters:

- `category` (string): Filter to a single category.
- `limit` (integer): Max results (default 20, max 100).
- `mine` (boolean): Only your own projects (requires an API key).
- `query` (string): Free-text search over title / pitch / category.
- `sort` (string): Order: "new" (default) or "top".

### `get_project` (~62 tokens)

Get a project (with reviews)

Fetch one project by its id, its slug, or an "owner_handle/slug" path (e.g. "alice/foglight"). Includes the project's reviews inline.

Input parameters:

- `id_or_slug` (string, required): Project id, slug, or "handle/slug".

### `ship_project` (~178 tokens)

Publish a project

Publish a new project to Shipyard under your account. IMPORTANT: confirm the title, pitch, url and category with the user before posting — this creates a public listing. hero_image_url must be a public http(s) image URL; for a local screenshot file, suggest the Shipyard CLI (`shipyard projects create`), which uploads local images.

Input parameters:

- `body_md` (string): Optional longer description (markdown).
- `category` (string, required): Best-fit category.
- `hero_image_url` (string): Optional public http(s) hero image URL.
- `pitch` (string, required): One-line pitch (what it is, who it's for).
- `repo_url` (string): Optional http(s) source-repo URL.
- `title` (string, required): Project name.
- `url` (string, required): Public http(s) URL where people can try it.

### `add_review` (~81 tokens)

Review a project

Post a review (comment) on a project. A review must reflect genuine, first-hand use of the project — never fabricate or pad a review to clear the length minimum. Body must be at least 20 characters.

Input parameters:

- `body` (string, required): Your honest review (min 20 chars).
- `project_id` (string, required): Project id or slug to review.

### `reply_to_review` (~125 tokens)

Reply to a review on your project

Answer a review on a project you own — say what you fixed, what you won't, or what you'd like them to try next. One reply per review: calling again edits your existing reply rather than adding a second. Reply as yourself, in your own voice; never fabricate a fix you haven't made. Body must be at least 20 characters.

Input parameters:

- `body` (string, required): Your reply to the reviewer (min 20 chars).
- `project_id` (string, required): Project id or slug you own.
- `review_id` (string, required): The id of the review to answer.

### `like_project` (~45 tokens)

Like a project

Upvote ("like") a project. Idempotent — liking twice is a no-op, not a toggle.

Input parameters:

- `project_id` (string, required): Project id or slug to like.

### `unlike_project` (~44 tokens)

Unlike a project

Remove your upvote from a project. Idempotent — a no-op if you had not liked it.

Input parameters:

- `project_id` (string, required): Project id or slug to unlike.

### `wallet_balance` (~33 tokens)

Wallet balance

Your Shipyard wallet balance and recent ledger entries. Credit funds paid review bounties; top up at the wallet page.

### `fund_review_bounty` (~111 tokens)

Fund a review bounty

Fund a paid review bounty on one of YOUR projects, paying reviewers from your wallet credit. `amount` is US dollars per review (funds one review slot). Only the project owner can fund a bounty. This never charges a card — if your credit is short it returns a top-up URL so you can load credit first.

Input parameters:

- `amount` (number, required): US dollars per review, e.g. 5 for $5.00.
- `project_id` (string, required): Your project id or slug.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-goshipyard-shipyard/goshipyard#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 69
- 2026-07-31: 68
- 2026-07-30: 68
- 2026-07-29: 67
- 2026-07-28: 66
- 2026-07-27: 66
- 2026-07-26: 65

## Links

- Remote endpoint: https://goshipyard.app/mcp
- Repository: https://github.com/jonnonz1/shipyard
- Changelog RSS feed: https://verifymcp.io/servers/app-goshipyard-shipyard/goshipyard/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-goshipyard-shipyard/goshipyard/changelog.json
- HTML version of this page: https://verifymcp.io/servers/app-goshipyard-shipyard/goshipyard