app.goshipyard/shipyard
REMOTE · GOSHIPYARD.APP · SCANNED SEP 22
Ship, discover and review vibe-coded projects on Shipyard, the invite-only feed for AI-built apps.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 992 tokens (~110/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety88
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ship_project" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the app.goshipyard/shipyard MCP server?
app.goshipyard/shipyard is a hosted endpoint at https://goshipyard.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · goshipyard.app
claude mcp add --transport http app-goshipyard-shipyard 'https://goshipyard.app/mcp'
{
"mcpServers": {
"app-goshipyard-shipyard": {
"url": "https://goshipyard.app/mcp"
}
}
} {
"servers": {
"app-goshipyard-shipyard": {
"type": "http",
"url": "https://goshipyard.app/mcp"
}
}
} [mcp_servers.app-goshipyard-shipyard] url = "https://goshipyard.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-goshipyard-shipyard": {
"type": "remote",
"url": "https://goshipyard.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-goshipyard-shipyard --url 'https://goshipyard.app/mcp' --transport streamable-http
mcp_servers:
app-goshipyard-shipyard:
url: "https://goshipyard.app/mcp" {
"McpServers": {
"app-goshipyard-shipyard": {
"Transport": "http",
"Url": "https://goshipyard.app/mcp"
}
}
} assistant mcp add app-goshipyard-shipyard -t streamable-http -u 'https://goshipyard.app/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 9 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- “list_projects” added an optional parameter “offset” cosmetic
- 26 Aug 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://goshipyard.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=goshipyard.app | CN=YE1,O=Let's Encrypt,C=US | 1 Sept 2026 | 30 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6aa75fb0f909e14107301677bcb8e73ebfb |
| SANs: *.goshipyard.app, goshipyard.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of goshipyard.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| goshipyard.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), camera=(), microphone=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://goshipyard.app/mcp | Verified | 200 | |
| http (plaintext) | http://goshipyard.app/mcp | HTTPS enforced | 301 | https://goshipyard.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_review Review a project ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Your honest review (min 20 chars). |
| project_id | string | yes | Project id or slug to review. |
No output schema declared.
No examples provided.
fund_review_bounty Fund a review bounty ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | US dollars per review, e.g. 5 for $5.00. |
| project_id | string | yes | Your project id or slug. |
No output schema declared.
No examples provided.
get_project Get a project (with reviews) ~62
Fetch one project by its id, its slug, or an "owner_handle/slug" path (e.g. "alice/foglight"). Includes the project's reviews inline.
| Name | Type | Req | Description |
|---|---|---|---|
| id_or_slug | string | yes | Project id, slug, or "handle/slug". |
No output schema declared.
No examples provided.
like_project Like a project ~45
Upvote ("like") a project. Idempotent — liking twice is a no-op, not a toggle.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | Project id or slug to like. |
No output schema declared.
No examples provided.
list_projects List / search projects ~166
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
| offset | integer | – | Zero-based offset (default 0, max 1000000). Pass pagination.next_offset to continue the same query. |
| query | string | – | Free-text search over title / pitch / category. |
| sort | string | – | Order: "new" (default) or "top". |
No output schema declared.
No examples provided.
reply_to_review Reply to a review on your project ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Your reply to the reviewer (min 20 chars). |
| project_id | string | yes | Project id or slug you own. |
| review_id | string | yes | The id of the review to answer. |
No output schema declared.
No examples provided.
ship_project Publish a project ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body_md | string | – | Optional longer description (markdown). |
| category | string | yes | Best-fit category. |
| hero_image_url | string | – | Optional public http(s) hero image URL. |
| pitch | string | yes | One-line pitch (what it is, who it's for). |
| repo_url | string | – | Optional http(s) source-repo URL. |
| title | string | yes | Project name. |
| url | string | yes | Public http(s) URL where people can try it. |
No output schema declared.
No examples provided.
unlike_project Unlike a project ~44
Remove your upvote from a project. Idempotent — a no-op if you had not liked it.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | Project id or slug to unlike. |
No output schema declared.
No examples provided.
wallet_balance Wallet balance ~33
Your Shipyard wallet balance and recent ledger entries. Credit funds paid review bounties; top up at the wallet page.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the app.goshipyard/shipyard MCP server?
app.goshipyard/shipyard is an MCP server listed in the public MCP registry as app.goshipyard/shipyard. Ship, discover and review vibe-coded projects on Shipyard, the invite-only feed for AI-built apps. This page covers its hosted endpoint (https://goshipyard.app/mcp).
Is the app.goshipyard/shipyard MCP server safe to use?
app.goshipyard/shipyard scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the app.goshipyard/shipyard MCP server expose?
app.goshipyard/shipyard exposes 9 tools: list_projects, get_project, ship_project, add_review, reply_to_review, and 4 more. Their descriptions and schemas cost roughly 845 tokens of context every time the server is loaded.
Does the app.goshipyard/shipyard MCP server require authentication?
No. We connected to app.goshipyard/shipyard without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the app.goshipyard/shipyard MCP server still maintained?
app.goshipyard/shipyard is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.