Shipswiftcomponents Mcp

com.clauxel.shipswiftcomponentsPublished by shipswiftcomponents.clauxel.comOfficial publisherv1.0.0Updated Oct 24, 2026

A paid remote MCP for ShipSwift, built to return verdicts, receipts, usage logs, and audit-ready JSO

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Paid remote MCP for ShipSwift that lets an assistant search SwiftUI components, generate component patches, check dependency policy and export receipts.

What you can do
  • Search SwiftUI components by query
  • Generate component patches for a project
  • Validate dependency policy against a component
  • Export component receipts as audit-ready JSON evidence
  • Return verdicts, usage logs and structured receipts alongside results
When to use it
Worth adding when you work on SwiftUI apps and want an assistant to find ShipSwift components, draft patches, check dependency rules and keep auditable records of what was done.
Requirements
Remote Streamable HTTP endpoint at shipswiftcomponents.clauxel.com/mcp; an MCP client that supports remote Streamable HTTP servers. A paid plan chosen on the product website and a bearer token sent in the Authorization header are required for production calls.
Before you install
It is a paid hosted service, so using it involves a subscription or billing arrangement. The bearer token is a credential: keep it out of shared configs and logs. Requests and usage are logged by the provider, and generated patches or dependency verdicts should be reviewed before applying them to a codebase.

Installation

In SourceWeft

  1. Open Shipswiftcomponents Mcp 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/com.clauxel.shipswiftcomponents%2Fshipswiftcomponents-mcp/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": {
    "shipswiftcomponents": {
      "type": "http",
      "url": "https://shipswiftcomponents.clauxel.com/mcp"
    }
  }
}

README

ShipSwift Component MCP

ShipSwift Component MCP remote MCP for ShipSwift.

Paid remote MCP for ShipSwift, structured receipts, usage logs, and audit-ready JSON evidence.

Public Endpoints

Access

This is a paid hosted remote MCP. Production calls require a bearer token issued from the product website.

http
Authorization: Bearer <token>

Unauthenticated browser visits to /mcp return a clear JSON error instead of internal details.

Tools

  • search_swiftui_component
  • generate_component_patch
  • validate_dependency_policy
  • export_component_receipt

Quick Start

  1. Open the website and choose a plan.
  2. Create or request an API token.
  3. Add the endpoint to an MCP client that supports Streamable HTTP remote servers.
  4. Send JSON-RPC requests with the bearer token.

Useful Links

Status

This repository is a public documentation and directory-submission reference for the hosted service. It does not contain the private production source code.

Source: README.md at commit 2c9197c

Tools

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

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% 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
  • 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
  • License10 pts

    Declare a license in the repository or the registry entry.