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.

Fudge for Shopify

REMOTE · MCP.FUDGE.AI

Run your Shopify store with AI: drafts you approve, what to fix, and how your store is doing.

Available components

+3 this week 70 Trust /100

Last scanned (12 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

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 Security63
Transport & Reachability100
Schema Quality & AI Usability72
  • 89% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 11543 tokens (~167/item across 69 items; 68 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 77% of tool parameters carry a description.Partial
Tool Safety92
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 2 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "request_publish_review" implies "publish" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 70 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
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_page” rewrote its description, which is the text the model reads security
    • Tool “check_page_speed” rewrote its description, which is the text the model reads security
    • Tool “find_context” rewrote its description, which is the text the model reads security
    • Tool “read_store_document” rewrote its description, which is the text the model reads security
    • Tool “read_work” rewrote its description, which is the text the model reads security
    • Schema quality: 145 → 167 ▼ functional
    • New prompt “seo_queue” functional
    • New tool “read_store_activity” functional
    • New tool “run_seo_tool” functional
  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 0
    • Tool “get_store_audit_result” rewrote its description, which is the text the model reads security
    • Tool “list_store_audits” rewrote its description, which is the text the model reads security
    • Tool “run_ai_readiness_check” rewrote its description, which is the text the model reads security
    • Tool “run_catalog_data_audit” rewrote its description, which is the text the model reads security
    • New tool “list_audit_runs” functional
    • New tool “read_audit_evidence” functional
  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “list_store_audits” rewrote its description, which is the text the model reads security
    • Schema quality: 7784 → 9344 ▼ functional
    • New prompt “bfcm_readiness” functional
    • New tool “check_ai_visibility” functional
    • New tool “check_product_schema” functional
    • New tool “find_missing_pages” functional
    • New tool “find_page_two_pages” functional
    • New tool “record_discovery_source” functional
    • New tool “run_bfcm_audit” functional
    • New tool “run_seo_report” functional
  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 0
    • Tool “edit_draft_file” rewrote its description, which is the text the model reads security
    • Tool “list_offers” rewrote its description, which is the text the model reads security
    • Tool “read_draft_file” rewrote its description, which is the text the model reads security
    • “write_draft_file” reworded the description of “content” cosmetic
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 21 Nov 2026 · Probed https://mcp.fudge.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.fudge.ai CN=YR1,O=Let's Encrypt,C=US 6 Nov 2026 4 Feb 2027 RSA 2048 SHA256-RSA 640c8fb90e6889caeae1f68a57b45d2d534
SANs: mcp.fudge.ai
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
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 mcp.fudge.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
fudge.ai. No DS 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://mcp.fudge.ai/mcp Verified 200
http (plaintext) http://mcp.fudge.ai/mcp HTTPS enforced 308 https://mcp.fudge.ai/mcp
MCP tools · 68 exposed · ~11,127 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
capture_page ~185

Screenshot one store page in a real browser on desktop and/or mobile and return the images. Pass `draft` to see a Fudge draft. `fullPage` captures top to bottom. Takes 15–60 seconds; up to 50 captures per store per day.

NameTypeReqDescription
devicestring––
draftstring–A draft’s fudge://project/… ref: capture the page as that draft shows it. Staged product and page content changes appear only on Fudge’s review page, not here.
fullPageboolean––
pagestring–A store URL or path, e.g. / or /products/blue-runner. Defaults to the home page, or with `draft` to the page the draft is about.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

check_ai_visibility ~259

Asks the public ChatGPT, Google AI Mode and Gemini apps 18 shopping questions written from a Shopify store’s catalogue in its market’s language, plus what the store is known for and, on ChatGPT, its returns and free shipping. Reports an AI visibility score; how often each assistant names the store, cites its pages or shows its products, by product line; who the answers name most often and which sources they cite; how AI describes the store; and whether ChatGPT states its return window and free-shipping threshold correctly. Real app answers, signed out, not model APIs. Free, no sign-in; waits up to 45 seconds, the first answers arrive within a minute and the rest within about 5. Shared per store for a day; unmeasured items are reported as unknown.

NameTypeReqDescription
countrystring–The market to check, as a two-letter ISO country code such as GB. Omit it for the store’s main market.
domainstring–The Shopify storefront to check, e.g. example.com. Required until a store is connected; afterwards, omit it to use a connected store.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

check_catalog_data ~223

Check catalogue data coverage across published products, collections, pages and articles: taxonomy, SEO fields, product type, vendor, description, images, alt text and optionally GTIN and MPN. Without `type`, totals and per-field coverage; with `type`, the items missing fields, a page at a time. The first call scans the live catalogue and can return status "scanning". Results are kept for an hour.

NameTypeReqDescription
includeProductIdentifiersboolean–Also check GTIN/barcode and MPN on products. A separate, slower scan.
limitinteger––
missingstring–With type: only items missing this field, named as in the summary, e.g. "Meta description".
offsetinteger––
refreshboolean–Rescan instead of reusing this hour’s result. Only after the merchant changed catalogue data.
storestring–The connected store to use. Omit when only one is connected.
typestring–List this type’s offenders instead of the summary.

No output schema declared.

No examples provided.

check_page ~145

Check one live store page’s server HTML for SEO and structured data, as browsers and Google read it: page head, title, canonical, noindex, structured data in JSON-LD, microdata or RDFa, lang, viewport, image alt text, mixed content and word count.

NameTypeReqDescription
domainstring–The Shopify storefront to check, e.g. example.com. Required until a store is connected; afterwards, omit it to use a connected store.
pagestring–A store URL or path, e.g. / or /products/blue-runner.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

check_page_speed ~184

Measure a store page with Google PageSpeed Insights: Lighthouse score and lab metrics, real-visitor Core Web Vitals, the largest improvement opportunities and a diagnosis of the cause (LCP element and phases, request chain, render-blocking requests, third parties, layout-shift culprits). Each device takes 10–30 seconds; results are cached for an hour. On a password-protected store, only real-visitor data is available.

NameTypeReqDescription
devicestring––
domainstring–The Shopify storefront to check, e.g. example.com. Required until a store is connected; afterwards, omit it to use a connected store.
pagestring–A store URL or path, e.g. / or /products/blue-runner.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

check_product_schema ~230

Checks up to 12 of a Shopify store’s product pages, spread over product types, sale and stock, against Google’s merchant listing and product rich result rules, using Google’s Required, Recommended and Agreement levels and wording. It compares each page’s markup with Shopify’s own product data and Shopify Catalog, checks the product list for missing descriptions, images, brands, categories and buyer details and whether Shopify Catalog searches find the right products, and, when the markup lacks the store’s policies, returns a paste-ready return and shipping policy JSON-LD block built only from its own policy pages, saying where in the theme it goes. Free, no sign-in; waits up to 45 seconds of a run’s usual 2–4 minutes. Shared per store for an hour. Anything it could not check is reported as unknown.

NameTypeReqDescription
domainstring–The Shopify storefront to check, e.g. example.com. Required until a store is connected; afterwards, omit it to use a connected store.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

check_store_technical ~98

Check the live store’s crawlability for search and AI: robots.txt rules, /llms.txt, sitemap.xml, password protection and whether products are publicly reachable.

NameTypeReqDescription
domainstring–The Shopify storefront to check, e.g. example.com. Required until a store is connected; afterwards, omit it to use a connected store.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

connect_store ~38

Create a link the merchant opens to connect another Shopify store. Use when they ask to add a store. The link works once within 10 minutes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

create_draft_article ~80

Create a new blog article in a Fudge draft. It can be previewed in the draft and goes live when the merchant publishes.

NameTypeReqDescription
articleobjectyes–
draftstringyesThe draft’s fudge://project/… ref.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

create_draft_collection ~87

Create a new hidden collection in a Fudge draft. It is deleted if the draft is discarded and goes live when the merchant publishes. Use only when the merchant asks.

NameTypeReqDescription
collectionobjectyes–
draftstringyesThe draft’s fudge://project/… ref.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

create_draft_page ~86

Create a new Shopify page in a Fudge draft, optionally with its own template. It can be previewed in the draft and goes live when the merchant publishes.

NameTypeReqDescription
draftstringyesThe draft’s fudge://project/… ref.
pageobjectyes–
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

create_draft_product ~96

Create a new hidden product in a Fudge draft, with options, variants, prices and media. It is deleted if the draft is discarded and becomes active when the merchant publishes. Use only when the merchant asks.

NameTypeReqDescription
draftstringyesThe draft’s fudge://project/… ref.
productobjectyes–
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

create_plan ~138

Start a new Plan for a goal the merchant has agreed and no existing Plan covers, with a title, areas, milestones and an optional brief. Schedules and recurring work are approved in Fudge.

NameTypeReqDescription
areasarrayyesAreas the Plan serves; empty for store-wide work.
briefstring–Markdown brief: goal, audience, decisions and constraints. Saved as brief.md in the Plan.
milestonesarrayyes–
storestring–The connected store to use. Omit when only one is connected.
titlestringyesShort outcome-focused title, e.g. “Rank for trail running shoes”.

No output schema declared.

No examples provided.

create_store_document ~108

Create a document inside an existing Plan, such as .plans/<slug>/brief.md, or with `replace` rewrite a whole document that was just read.

NameTypeReqDescription
contentstringyesComplete document content.
pathstringyesDestination path, for example .plans/<slug>/brief.md.
replaceboolean–True to replace an existing document you have read in full.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

delete_draft_file ~133

Delete a theme file from a Fudge draft, or stage removal of an item by its .entities path. Fudge refuses deletions that would break references. Publishing applies the removal; until then it can be undone.

NameTypeReqDescription
draftstringyesThe draft’s fudge://project/… ref.
pathstringyesA theme file such as sections/main-product.liquid or templates/product.json, or a content document such as .entities/product/123.jsonc or .entities/page/45.body.html.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

edit_draft_content ~238

Change products, collections, pages, articles, blogs and their metafields in a Fudge draft with sparse patches, many items in one call. - Name only the fields you change; nested objects such as seo merge per key. - Rows with an "id" (variants, options, media) merge by id; omit "id" to add a row; {"id": …, "_delete": true} removes one. Variants and media live at .entities/product/{id}/variants.jsonc and media.jsonc. - Lists such as tags take a full array or {"add": […], "remove": […]}. - Metafields: .entities/product/{id}.metafields with {"namespace.key": {"type": …, "value": …}}; "value": null removes one. Changes to existing items are staged for the merchant’s review. Items the draft created change in Shopify at once.

NameTypeReqDescription
draftstringyesThe draft’s fudge://project/… ref.
editsarrayyes–
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

edit_draft_file ~146

Change part of a theme file or .entities document in a Fudge draft by replacing exact text, without line gutters. Fudge validates the result and refreshes the preview.

NameTypeReqDescription
draftstringyesThe draft’s fudge://project/… ref.
editsarrayyes–
pathstringyesA theme file such as sections/main-product.liquid or templates/product.json, or a content document such as .entities/product/123.jsonc or .entities/page/45.body.html.
revisionstring–The revision returned when this file was read.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

edit_store_document ~123

Change part of a store document, such as a Plan’s brief or the design guide, by replacing exact text. Fails if the text is gone or the document has changed since it was read.

NameTypeReqDescription
new_stringstringyesReplacement text; empty deletes old_string.
old_stringstringyesExact text to replace.
pathstringyesPath of the existing document.
replace_allboolean–Replace every occurrence. Defaults to false.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

find_context ~141

Search what Fudge knows about this store: memory guides, Plans, projects, findings, recommendations, recorded changes, messages between Fudge’s agents and past conversations. Pass `about` (a URL, Shopify GID or fudge:// ref) for everything related to one thing. Conversation results say whether the work is a draft, was published or was only discussed.

NameTypeReqDescription
aboutstring–ID, storefront URL/path or file that results must relate to.
cursorstring––
querystring––
storestring–The connected store to use. Omit when only one is connected.
whereobject––

No output schema declared.

No examples provided.

find_keyword_ideas ~139

Find longer search phrases containing a seed keyword, with volume, difficulty and intent. Changes nothing and uses no credits; each store has a daily limit.

NameTypeReqDescription
languagestring–Language code, e.g. "en". Defaults to the store’s language.
limitinteger––
locationstringyesTarget country, e.g. "United States". Ask the merchant which countries they sell to if unknown.
maxDifficultynumber––
minVolumeinteger––
seedstringyes–
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

find_missing_pages ~227

Builds the Google searches for what a Shopify store sells from its catalogue (each kind of product with its attributes and audiences), keeps those a model judges are for its products, and checks the largest it has no collection for on Google today. Returns the missing pages worth building, with monthly searches and who ranks, and collections Google doesn’t show for searches they cover. Uses DataForSEO Google data and the store’s public catalogue. Free, no sign-in; waits up to 45 seconds of a run’s usual 1–4 minutes. Shared per store for 7 days. Anything it could not judge is reported as unknown, never as a finding.

NameTypeReqDescription
countrystring–The market to check, as a two-letter ISO country code such as GB. Omit it for the store’s main market.
domainstring–The Shopify storefront to check, e.g. example.com. Required until a store is connected; afterwards, omit it to use a connected store.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

find_page_two_pages ~230

Finds a Shopify store’s collections, pages and articles that rank #4–20 on Google in the store’s market (DataForSEO rankings), checks the most valuable on Google today, and gives each one’s searches, monthly volumes, a range of extra clicks from reaching #3 and the change it needs, plus pages that were near page one and have left the top 20, with the cause found. One rewritten title is previewed as a Google result. Free, no sign-in; waits up to 45 seconds of a run’s usual 1–4 minutes. Shared per store for 7 days; anything not measured is reported as not checked.

NameTypeReqDescription
countrystring–The market to check, as a two-letter ISO country code such as GB. Omit it for the store’s main market.
domainstring–The Shopify storefront to check, e.g. example.com. Required until a store is connected; afterwards, omit it to use a connected store.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

get_design_guide ~71

Read the store’s design guide: colours, typography, spacing, components and brand voice. Use when designing or reviewing pages. With no guide yet and a distinctive theme, this starts a one-time extraction.

NameTypeReqDescription
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

get_keyword_metrics ~129

Get Google search volume, difficulty, intent, CPC and 12-month history for specific keywords in one country. Missing values are unknown, not zero. Changes nothing and uses no credits; each store has a daily limit.

NameTypeReqDescription
keywordsarrayyes–
languagestring–Language code, e.g. "en". Defaults to the store’s language.
locationstringyesTarget country, e.g. "United States". Ask the merchant which countries they sell to if unknown.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

get_ranked_keywords ~169

List the Google searches a domain ranks for in one country, with position, URL, volume, difficulty and estimated traffic. Defaults to this store; pass a competitor’s domain to compare. Changes nothing and uses no credits; each store has a daily limit.

NameTypeReqDescription
domainstring–Defaults to this store’s domain.
languagestring–Language code, e.g. "en". Defaults to the store’s language.
limitinteger––
locationstringyesTarget country, e.g. "United States". Ask the merchant which countries they sell to if unknown.
pathPrefixstring–Only URLs under this path, e.g. /blogs/.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

get_search_results ~136

Read Google’s live first results page for one search in one country: ranked results, features, AI Overview citations, People Also Ask and related searches. Changes nothing and uses no credits; each store has a daily limit.

NameTypeReqDescription
devicestring––
keywordstringyes–
languagestring–Language code, e.g. "en". Defaults to the store’s language.
locationstringyesTarget country, e.g. "United States". Ask the merchant which countries they sell to if unknown.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

get_store_audit_result ~145

Read the latest full audit: status, result card and report links. Quick checks are previews, not completed audits. A previous successful report is linked separately when the latest run has not completed. Reading starts nothing. `waitSeconds` waits up to 50 seconds for a running report.

NameTypeReqDescription
auditstringyesThe diagnostic’s id.
domainstring–The Shopify storefront to check, e.g. example.com. Required until a store is connected; afterwards, omit it to use a connected store.
storestring–The connected store to use. Omit when only one is connected.
waitSecondsinteger–Default 0.

No output schema declared.

No examples provided.

get_store_insights ~212

Read the findings and recommendations Fudge has saved for this store, most important first; narrow by area, subject, kind, date or text. With `ref`, one record in full with its sources and measurements. An empty list means nothing is saved yet. This never starts an investigation.

NameTypeReqDescription
areastring–seo, ai-discovery, conversion or merchandising, or a library such as landing-pages or quizzes.
kindstring––
limitinteger––
querystring–Words to find in the title, summary or body.
refstring–Read one record in full; the other filters are ignored.
sincestring–Only records created or updated on or after this date.
storestring–The connected store to use. Omit when only one is connected.
subjectstring–A product, collection, page or article ID (product-42 or a Shopify GID), or a Fudge Plan ref.

No output schema declared.

No examples provided.

get_store_overview ~112

Read a store’s overview: business context, standing memory, Google connection, work waiting on the merchant, Plans, top recommendations and recent results. With `area`, that area’s findings, Plans, work, outputs and headline numbers. Use for a brief or before planning work.

NameTypeReqDescription
areastring–seo, ai-discovery, conversion or merchandising, or a library such as landing-pages or blog.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

get_store_performance ~312

Measure the store, or a product, collection, page, article or URL given as `subject`. `metrics` returns headline values with their previous period, definition and source. `breakdown` returns ranked rows such as queries, landing pages, channels, AI assistants, devices, countries, products or discount codes. With neither, returns what exists for the subject. Periods default to the 28 days ending three days ago against the 28 days before. Google Analytics, Search Console and Shopify are separate measurements.

NameTypeReqDescription
ascendingboolean––
breakdownstring––
compareboolean––
comparisonEndstring––
comparisonStartstring––
countrystring–Search Console three-letter country code, e.g. usa.
days–––
devicestring––
endDatestring––
limitinteger––
metricsarray––
offsetinteger––
sortstring–Breakdown metric to rank by, e.g. clicks, impressions, sessions, revenue, orders.
startDatestring––
storestring–The connected store to use. Omit when only one is connected.
subjectstring–What to measure: a product, collection, page or article ID (product-42 or a Shopify GID), its name or handle, a storefront URL or path (/products/x), or omit for the whole store.

No output schema declared.

No examples provided.

list_audit_runs ~160

List retained free audit runs for the store, newest first, with stable run ids, dates and a continuation cursor. Reads only; never starts collection or spends audit allowance.

NameTypeReqDescription
auditstringyes–
countrystring–Two-letter ISO country code, such as GB.
cursorstring–The nextCursor from the previous page; maximum 1,000 characters.
domainstring–The Shopify storefront to check, e.g. example.com. Required until a store is connected; afterwards, omit it to use a connected store.
limitnumber–Integer from 1 to 100 runs per page.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

list_offers ~71

List the store’s current offers: Fudge offers, active Shopify discounts, native bundles, and shipping rates by zone or market with their free-shipping conditions. Use for an offers or average-order-value review.

NameTypeReqDescription
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

list_store_audits ~89

List the audits Fudge can run for this store: the Knowledge Base diagnostic, free SEO and BFCM audits and eight agent reviews, with each one’s latest result: a free audit’s status, check date, headline, score and result page. Listing starts nothing and spends nothing.

NameTypeReqDescription
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

list_stores ~18

List the Shopify stores this connection can use.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_work ~119

List Fudge work for this store, including work started in Fudge or another assistant. `view: "needs_you"` returns what is waiting on the merchant. `query` searches past work.

NameTypeReqDescription
beforestring––
kindstring––
limitnumber–1–50, default 20.
querystring–Ranked search; cannot be combined with before.
storestring–The connected store to use. Omit when only one is connected.
viewstring––

No output schema declared.

No examples provided.

message_fudge ~205

Ask Fudge to do work for this store: build or revise a page, article or other draft, investigate, or answer a question. Without `ref`, starts a new conversation; with `ref`, continues that work. Uses the store’s Fudge credits. `requestId` makes retries deliver once. Publishing always needs the merchant’s own approval in Fudge.

NameTypeReqDescription
deliverystring––
messagestringyesThe merchant’s request in full: what to do, for which page or products, and any decisions already made.
refstring–fudge://thread/… or fudge://project/… to continue; omit to start new work.
requestIdstringyesA unique ID you choose for this request, e.g. a UUID. Retries reuse it.
storestring–The connected store to use. Omit when only one is connected.
titlestring–Short title for a new conversation.

No output schema declared.

No examples provided.

open_fudge_home ~69

Open Fudge Home for a store: work waiting on the merchant, the next recommended step and the four growth areas. Use when the merchant asks to open Fudge or see their store at a glance.

NameTypeReqDescription
storestring–The connected store to use. Defaults to the first one.

No output schema declared.

No examples provided.

read_audit_evidence ~205

Read complete retained evidence from a free audit run, including full AI answers, sources, product records and findings. Discovers named collections, then returns selected records with explicit pagination and availability. Reads only; never starts collection or spends audit allowance.

NameTypeReqDescription
auditstringyes–
domainstring–The Shopify storefront to check, e.g. example.com. Required until a store is connected; afterwards, omit it to use a connected store.
limitnumber–Integer from 1 to 100 child records. Strings use 10,000-character pages.
offsetnumber–Non-negative integer; use the previous page’s nextOffset.
recordIdstring–A returned JSON-pointer record id; maximum 2,000 characters.
runIdstringyesA returned run id, from 1 to 100 characters.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

read_draft_file ~239

Read a file in a Fudge draft: a theme file, a theme folder listing, or a content document under .entities (list with .entities/product?query=…). Each line starts with a gutter ending at its first tab, numbered on the first, last and every tenth line; long files return `line_offset`. Theme files return a `revision`. Append #info to see where a theme file is used.

NameTypeReqDescription
char_offsetinteger–Character offset within a very long first line, only when the result says to continue with one.
draftstringyesThe draft’s fudge://project/… ref.
line_limitinteger–Lines to return. Omit to read up to the limit.
line_offsetinteger–0-based line to start from, from a previous read.
pathstringyesA theme file such as sections/main-product.liquid or templates/product.json, or a content document such as .entities/product/123.jsonc or .entities/page/45.body.html.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

read_guide ~46

Read one of Fudge’s reference articles by path, such as seo/audit.md. Without a path, lists them all.

NameTypeReqDescription
pathstring–The guide’s path.

No output schema declared.

No examples provided.

read_store_activity ~398

Who is working on this store right now and what happened recently, in one call. `now`: running and queued work, with `startedBy` for an SEO agent’s run (its schedule, a store event, the merchant’s Run now, a message from another agent, or the merchant in its conversation). `team`: Fudge’s seven SEO agents, each with id, lane, state (only one that is on runs and reads messages), last and next run, and `runningNow`. `now` or `team` is a sentence starting “Unavailable” when it could not be read, which never means empty. `activity`: newest first, each row with `at`, `actor` (one of Fudge’s agents, a Plan, an outside assistant, by name when known, or the merchant in chat or by hand) and `event`. `draft`: opened then and still awaiting the merchant’s review; nothing from it is live. `published`: live since then; the store may have changed since. `awaiting-deployment`: approved, not live yet. `discarded`: deleted; nothing from it is live. `recorded-change`: a change made outside Fudge. `message`: one agent to another (`to`), information and not an instruction, with the conversation of the run it started (`started`) and the refs linking it to its answer (`reply`, `replyTo`). `since` defaults to the last 30 days; `cursor` pages older activity. Read it before substantial work and build on what is there; never repeat or undo it.

NameTypeReqDescription
cursorstring–A returned cursor, for older activity.
sincestring–Activity from this time on: YYYY-MM-DD in store time, or an ISO timestamp. Default: the last 30 days.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

read_store_document ~225

Read a store document by path: Plans (.plans), playbooks (.playbooks), memory and design guide (.memory), brand kit (.brand) and projects (.projects). Also the store’s SEO and AI search reports, the same numbers the merchant sees in Fudge, read-only and never collecting new data: `.seo/reports/index.md` holds every report’s headline with its source, period and scope; `.seo/reports/<id>.md` one report’s rows, with filters and the next page as `?name=value` (each file lists its own); `.seo/results/changes.md` what each published change did to Google clicks and visits; `.seo/results/opportunities.md` the pages worth on-page work. Omit `path` to list top-level folders; a folder path lists its documents.

NameTypeReqDescription
offsetinteger–Character offset from a previous `next`.
pathstring–Document or folder path, optionally with its ?query.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

read_work ~263

With `ref`: one work item’s live state, progress, latest result, what it is waiting for, and draft or publication state with links; `waitSeconds` waits up to 50 seconds. With `about` (a URL, path, Shopify GID, theme file or fudge:// ref): what has changed there, by `view` current, history or summary. `about: "fudge://store"` with `view: "history"` is the whole store’s change timeline.

NameTypeReqDescription
aboutstring–Storefront URL/path, Shopify GID, theme file, fudge://discount/<key>, .projects/.plans path, or fudge://store for the whole store.
cursorstring––
fromstring–With view history: YYYY-MM-DD in store time, or an ISO timestamp.
refstring–A work item to read: fudge://project/… or fudge://thread/….
storestring–The connected store to use. Omit when only one is connected.
tostring––
viewstring––
waitSecondsinteger–With ref: wait up to this long for running work to finish or need the merchant. Default 0.

No output schema declared.

No examples provided.

record_change ~207

Add a change made outside Fudge to the store’s timeline, such as ads, prices, apps, email, shipping or theme edits in Shopify, so later results can be attributed. Fudge’s own publishes are recorded automatically.

NameTypeReqDescription
atstring–When it took effect: YYYY-MM-DD or an ISO timestamp. Defaults to now.
linksarray–fudge:// references or Shopify GIDs of what the change affected, e.g. gid://shopify/Product/123.
storestring–The connected store to use. Omit when only one is connected.
surfacestringyesWhere: theme, catalogue, pricing, discounts, email, Meta ads, Google ads, apps, shipping or other.
whatstringyesWhat changed, concretely, e.g. "Raised Meta prospecting budget from €50 to €80 a day".
whystring–Intent or expected effect, so results can be checked against it later.

No output schema declared.

No examples provided.

record_discovery_source ~90

Save how the merchant heard about Fudge during setup. Record only their stated answer, or null if they explicitly skip. Never infer the source. Existing answers and skips are preserved; this changes no storefront content.

NameTypeReqDescription
answer–yesThe merchant’s own answer, or null only if they explicitly skip.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

remember ~199

Save a lasting rule, decision, correction or learning to store memory. Use when the user states how things should be done from now on, not for one-off requests. Duplicates change nothing; a contradiction comes back as a conflict.

NameTypeReqDescription
notestringyesThe lasting rule, decision or learning to keep, written as it should apply in future work, with its conditions, exceptions and reason. Not a one-off task or a detail of the current draft.
personalboolean–Save only for the person you are serving: how to work with them (language, tone, length, what to ask them). Default: shared with everyone working on this store. Never put a person's private details i…
replacesboolean–The user explicitly corrected or reversed an earlier rule. Replace the old rule instead of returning a conflict.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

request_publish_review ~90

Prepare a finished draft for the merchant’s publish decision. Returns the link to Fudge’s review page, what will change and whether publishing needs a plan. This does not publish; only the merchant can, in Fudge.

NameTypeReqDescription
refstringyesThe work’s fudge://project/… ref.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

run_ai_readiness_check ~162

Run Fudge’s free AI visibility audit: whether ChatGPT, Google AI Mode and Gemini name, cite or show the store for shopping questions in its main market, with a score and prioritized fixes. Takes about 5 minutes and waits up to 45 seconds. Reuses a running or fresh result unless `fresh` is true; an active run is always shared.

NameTypeReqDescription
domainstring–The Shopify storefront to check, e.g. example.com. Required until a store is connected; afterwards, omit it to use a connected store.
freshboolean–Start a new run even when a result from the last 24 hours exists.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

run_bfcm_audit ~239

Checks a Shopify store’s Black Friday readiness in four scored parts: gift searches its products fit (real monthly Google searches and the store’s position today, in its main market or the one `country` names), who is #1 for the store’s own "<brand> black friday" search and whether its sale states dates, how to get the discount and what’s included, its return, shipping and delivery details, and whether its public Shopify AI answers those questions correctly. Every problem comes with evidence and a fix brief. Free, no sign-in; waits up to 45 seconds, then returns progress and report links. Anything it could not check is reported as unchecked with its reason, never scored.

NameTypeReqDescription
countrystring–The market to check, as a two-letter ISO country code such as GB. Omit it for the store’s main market.
domainstring–The Shopify storefront to check, e.g. example.com. Required until a store is connected; afterwards, omit it to use a connected store.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

run_catalog_data_audit ~152

Run Fudge’s free product schema and catalogue audit: product markup, categories, product details and whether AI buyer searches find the right products, with a score and prioritized fixes. Waits up to 45 seconds. Reuses a running or fresh result unless `fresh` is true; an active run is always shared.

NameTypeReqDescription
domainstring–The Shopify storefront to check, e.g. example.com. Required until a store is connected; afterwards, omit it to use a connected store.
freshboolean–Start a new run even when a result from the last 24 hours exists.
storestring–The connected store to use. Omit when only one is connected.

No output schema declared.

No examples provided.

Install

How do I install the Fudge for Shopify MCP server?

Fudge for Shopify is a hosted endpoint at https://mcp.fudge.ai/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 · mcp.fudge.ai

# add to Claude Code
claude mcp add --transport http ai-fudge-fudge 'https://mcp.fudge.ai/mcp'
Common questions

What is the Fudge for Shopify MCP server?

Fudge for Shopify is an MCP server listed in the public MCP registry as ai.fudge/fudge. Run your Shopify store with AI: drafts you approve, what to fix, and how your store is doing. This page covers its hosted endpoint (https://mcp.fudge.ai/mcp).

Is the Fudge for Shopify MCP server safe to use?

Fudge for Shopify scores 70 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 Fudge for Shopify MCP server expose?

Fudge for Shopify exposes 68 tools: list_stores, record_discovery_source, connect_store, get_store_overview, search_design_references, and 63 more. Their descriptions and schemas cost roughly 11,127 tokens of context every time the server is loaded.

Does the Fudge for Shopify MCP server require authentication?

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

Is the Fudge for Shopify MCP server still maintained?

Fudge for Shopify is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Fudge for Shopify MCP server?

VerifyMCP ran 14 checks on Fudge for Shopify, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.