Home / MCP registry index / ai.fudge/fudge

Fudge for Shopify

ai.fudge/fudge in the official MCP registry. Endpoint https://mcp.fudge.ai/mcp. Source: github.com/fudge-ai/fudge-plugin.

The registry describes it as: Run your Shopify store with AI: drafts you approve, what to fix, and how your store is doing.

Connect it

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

claude mcp add --transport http fudge https://mcp.fudge.ai/mcp

{
  "mcpServers": {
    "fudge": {
      "url": "https://mcp.fudge.ai/mcp"
    }
  }
}

code --add-mcp '{"name":"fudge","type":"http","url":"https://mcp.fudge.ai/mcp"}'

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.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

list_stores connect_store get_store_overview search_design_references show_design_references get_store_performance get_store_insights get_design_guide search_guides read_guide find_context remember record_change read_store_document edit_store_document create_store_document create_plan list_store_audits run_ai_readiness_check run_catalog_data_audit run_knowledge_base_check get_store_audit_result check_page_speed check_store_technical check_page start_website_redesign start_store_builder check_catalog_data search_catalog list_offers capture_page get_keyword_metrics find_keyword_ideas get_search_results get_ranked_keywords list_work read_work message_fudge stop_work request_publish_review open_fudge_home show_draft start_draft read_draft_file search_draft_files edit_draft_file write_draft_file delete_draft_file edit_draft_content create_draft_product create_draft_collection create_draft_page create_draft_article show_preview_consent set_preview_consent send_feedback show_resources

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-10): 98497093767b2e75. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/ai-fudge-fudge/badge.svg)](https://lazaretto.dev/mcp-registry/ai-fudge-fudge)

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. How tool poisoning works. What we found across the registry. Check another server.

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

Related

E-commerce MCP servers