mcpbeat

Catalog Attribute Normalizer MCP Server

com.acjlabs/catalog-normalizer
answering

Catalog Attribute Normalizer is answering right now. Last checked 15 min ago. It exposes 1 tools. Last commit 2 Aug 2026.

Catalog attribute normalizer, taxonomy-grounded — no fabricated Google/Shopify category IDs.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
886 ms
Response time
average over 24h
2
Stars
last commit 2 Aug 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add catalog-normalizer --transport http https://catalog-normalizer.acjlabs.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "catalog-normalizer": {
      "url": "https://catalog-normalizer.acjlabs.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.catalog-normalizer]
url = "https://catalog-normalizer.acjlabs.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "catalog-normalizer": {
      "url": "https://catalog-normalizer.acjlabs.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "catalog-normalizer": {
      "url": "https://catalog-normalizer.acjlabs.com/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

normalize
normalize_catalog
Normalizes a batch of catalog products (attribute canonicalization/extraction + category-path mapping into the requested target taxonomies: google, shopify, amazon). Returns one result per input product, same order: a NormalizedProduct on success, or { error, source_title } if that specific product's classification failed — one product's failure never voids the rest of the batch. attributes is keyed by a controlled vocabulary (size, color, material, gender, sleeve_length — unrecognized keys are dropped, not passed through under a model-chosen name) and each value carries provenance: "canonicalized" means it came from your own raw_attributes input for that product (deterministic cleanup only, no recall); "extracted" means the model inferred it from the title/description and it wasn't in your input — treat extracted values as a suggestion, not a confirmed fact about the product, the same way you'd treat a low-confidence category_paths entry. category_paths for google and shopify is retrieval-grounded against the real, current taxonomy files (not recalled from memory) — measured at 22/24 (91.7%) exact path+leaf_id matches on a 12-product evaluation set; amazon has no comparable public reference file, so it stays best-effort. Each entry's confidence (0-1) and leaf_id (null when not confident it matches a real node) are the honest signal regardless of taxonomy — treat a low-confidence or null-leaf_id result as a suggestion worth a quick human check, not a confirmed classification.

Endpoints

URLTransportStateLatencyChecked
https://catalog-normalizer.acjlabs.com/mcp streamable-http answering 101 ms 15 min ago

Catalog Attribute Normalizer — questions

Answers built from our own checks of this server.

What can Catalog Attribute Normalizer do?
It exposes 1 tools, read directly from the server on our last check. Among them: normalize_catalog. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Catalog Attribute Normalizer working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 886 ms. The bar chart above shows every period we have measured.
How do I connect Catalog Attribute Normalizer?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Catalog Attribute Normalizer need an API key?
No. Catalog Attribute Normalizer completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Catalog Attribute Normalizer?
It answers our handshake in 886 ms on average, which is faster than 7% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Catalog Attribute Normalizer open source?
Yes — 2 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.