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.

AI Catalog by Crescendo Lab

REMOTE · CATALOG.CRESCLAB.COM

Check if a product feed is ready for AI shopping (ChatGPT, Gemini, AI Mode): score, gaps, fixes.

+4 this week 79 Trust /100

Last scanned (11 minutes ago)

Scores higher than 82% of remote servers

Reachable. Last reached 25 Oct 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 Security74
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 442 tokens (~147/item across 3 items; 3 tools + 0 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 Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
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.

  • 25 Oct 26 +1

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

  • 23 Oct 26 +1

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

  • 21 Oct 26 +1

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

  • 19 Oct 26 +1

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

  • 17 Oct 26 +1

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

  • 15 Oct 26 +1

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

  • 13 Oct 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.

  • 10 Oct 26 72

    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 25 Oct 2026 · Probed https://catalog.cresclab.com/api/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=catalog.cresclab.com CN=WR3,O=Google Trust Services,C=US 23 Sept 2026 22 Dec 2026 RSA 2048 SHA256-RSA 83b98cd92feb790e0960c108ea5e4570
SANs: catalog.cresclab.com
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of catalog.cresclab.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
cresclab.com. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://catalog.cresclab.com/api/mcp/ Verified 200
http (plaintext) http://catalog.cresclab.com/api/mcp/ HTTPS enforced 302 https://catalog.cresclab.com/api/mcp/
MCP tools · 3 exposed · ~286 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_feed_fix_guide ~85

Explain what a gap from scan_product_feed means, why AI shopping assistants need that data, and how to fix it with evidence the merchant already owns. Call with no argument to get the full checklist.

NameTypeReqDescription
issue_keystring–Issue key from scan_product_feed, e.g. no_specs, thin_desc, llm_unanswerable. Omit for all.

No output schema declared.

No examples provided.

list_ai_shopping_platforms ~55

List the main AI shopping surfaces and how product data reaches each one (e.g. Google Merchant Center for Gemini / AI Mode / Shopping; ChatGPT merchant program). Overview only, not a list of live integrations.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scan_product_feed ~146

Fetch a public product feed once and score how well AI shopping assistants can understand it (0-100). Returns the biggest gaps (share of products affected), sample shopper questions AI could not answer from the feed, the thinnest products, and a link to fix the gaps. Accepts Google Merchant / Facebook catalog XML, CSV, TSV, or a Shopify store URL. Takes 20-60 seconds. Only summary results are stored.

NameTypeReqDescription
feed_urlstringyesPublic URL of the product feed or Shopify store, e.g. https://example.com/feed.xml or https://shop.example.com
localestring–Language for shopper questions and labels (default en).

No output schema declared.

No examples provided.

Install

How do I install the AI Catalog by Crescendo Lab MCP server?

AI Catalog by Crescendo Lab is a hosted endpoint at https://catalog.cresclab.com/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 · catalog.cresclab.com

# add to Claude Code
claude mcp add --transport http com-cresclab-catalog-ai-catalog 'https://catalog.cresclab.com/api/mcp/'
Common questions

What is the AI Catalog by Crescendo Lab MCP server?

AI Catalog by Crescendo Lab is an MCP server listed in the public MCP registry as com.cresclab.catalog/ai-catalog. Check if a product feed is ready for AI shopping (ChatGPT, Gemini, AI Mode): score, gaps, fixes. This page covers its hosted endpoint (https://catalog.cresclab.com/api/mcp/).

Is the AI Catalog by Crescendo Lab MCP server safe to use?

AI Catalog by Crescendo Lab scores 79 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 AI Catalog by Crescendo Lab MCP server expose?

AI Catalog by Crescendo Lab exposes 3 tools: scan_product_feed, get_feed_fix_guide, list_ai_shopping_platforms. Their descriptions and schemas cost roughly 286 tokens of context every time the server is loaded.

Does the AI Catalog by Crescendo Lab MCP server require authentication?

No. We connected to AI Catalog by Crescendo Lab without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AI Catalog by Crescendo Lab MCP server still maintained?

AI Catalog by Crescendo Lab is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.