Home / MCP registry index / io.github.Travisswop/swop

io.github.Travisswop/swop

io.github.Travisswop/swop in the official MCP registry. Endpoint https://mcp.swopme.co/mcp/commerce. Source: github.com/Travisswop/swop-mcp.

The registry describes it as: Sell to people and AI agents: create products, a storefront, and USDC payment links from chat.

We read its 27 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http swop https://mcp.swopme.co/mcp/commerce

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "swop": {
      "url": "https://mcp.swopme.co/mcp/commerce"
    }
  }
}

VS Code

code --add-mcp '{"name":"swop","type":"http","url":"https://mcp.swopme.co/mcp/commerce"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

swop_search_identities swop_lookup_identity swop_get_help swop_get_my_profile swop_get_my_balances swop_get_my_orders swop_list_my_tokens swop_get_my_smartsite swop_update_my_smartsite swop_add_link swop_remove_link swop_create_feed_post swop_create_product swop_create_checkout swop_get_checkout swop_list_webhooks swop_register_webhook swop_test_webhook swop_remove_webhook swop_list_embed_origins swop_register_embed_origin swop_remove_embed_origin swop_feature_product swop_list_my_products swop_update_product swop_get_product_link swop_get_store

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-travisswop-swop/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-travisswop-swop)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.