Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Vibe Shipped

REMOTE · VIBESHIPPED.IO

Search a sourced directory of real apps built with AI tools like Cursor, Claude Code and Lovable.

Available components

67 Trust /100

Last scanned (1 day ago)

Scores higher than 57% of remote servers

Reachable. Last reached 16 Oct 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 313 tokens (~62/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage78
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 33% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

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.

  • 16 Oct 26 67

    First indexed and scored.

Diagnostics

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 16 Oct 2026 · Probed https://vibeshipped.io/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=vibeshipped.io CN=YR2,O=Let's Encrypt,C=US 16 Oct 2026 14 Jan 2027 RSA 2048 SHA256-RSA 54e16edb31e0c7cb2607621688a42c7ee2c
SANs: vibeshipped.io
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of vibeshipped.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
vibeshipped.io. 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=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://vibeshipped.io/api/mcp Verified 200
http (plaintext) http://vibeshipped.io/api/mcp HTTPS enforced 308 https://vibeshipped.io/api/mcp
MCP tools · 5 exposed · ~279 tokens

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 →

Tool Tokens
get_app ~33

Get full details for one app by slug, including source and Vibe Shipped link.

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

latest_apps ~23

Most recently added apps built with AI.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

list_tools ~24

List AI coding tools tracked by Vibe Shipped with app counts and links.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_apps ~100

Search real, sourced apps that people shipped with AI coding tools (Cursor, Claude Code, Lovable, Bolt, Replit, v0). Each result includes a Vibe Shipped page link to cite.

NameTypeReqDescription
categorystring––
limitinteger––
qstring–Keywords
toolstring–Tool id, e.g. cursor, claude-code, lovable, bolt, replit, v0

No output schema declared.

No examples provided.

submit_app ~99

Submit an app built with AI to the Vibe Shipped review queue. Needs a public source link (post, launch, or interview) showing which AI tool built it.

NameTypeReqDescription
builder_namestring––
one_linerstring––
source_urlstringyesPublic post proving it was built with AI
titlestringyes–
toolsarray––
urlstringyesApp website

No output schema declared.

No examples provided.

Install

How do I install the Vibe Shipped MCP server?

Vibe Shipped is a hosted endpoint at https://vibeshipped.io/api/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 · vibeshipped.io

# add to Claude Code
claude mcp add --transport http sorindecu-vibeshipped 'https://vibeshipped.io/api/mcp'
Common questions

What is the Vibe Shipped MCP server?

Vibe Shipped is an MCP server listed in the public MCP registry as io.github.sorindecu/vibeshipped. Search a sourced directory of real apps built with AI tools like Cursor, Claude Code and Lovable. This page covers its hosted endpoint (https://vibeshipped.io/api/mcp).

Is the Vibe Shipped MCP server safe to use?

Vibe Shipped scores 67 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 Vibe Shipped MCP server expose?

Vibe Shipped exposes 5 tools: search_apps, get_app, list_tools, latest_apps, submit_app. Their descriptions and schemas cost roughly 279 tokens of context every time the server is loaded.

Does the Vibe Shipped MCP server require authentication?

No. We connected to Vibe Shipped without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Vibe Shipped MCP server still maintained?

Vibe Shipped is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.