Catalog Attribute Normalizer
v0.1.2Catalog attribute normalizer, taxonomy-grounded — no fabricated Google/Shopify category IDs.
Endpoint health
online- Last checked
- 11/20/2026, 6:18:01 AM
- Latency
- 1492 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.acjlabs%2Fcatalog-normalizer
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.acjlabs/catalog-normalizer": {
"url": "https://catalog-normalizer.acjlabs.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
1 shown · authentication unknown
Normalize Catalog
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.
Schema valid · SHA-256 f8e7c79cc6d6…
View input schema
{ "type": "object", "properties": { "products": { "maxItems": 200, "type": "array", "items": { "type": "object", "properties": { "title": { "type": "string", "maxLength": 500 }, "description": { "type": "string", "maxLength": 5000 }, "raw_attributes": { "type": "object", "propertyNames": { "type": "string" }, "additionalProperties": { "type": "string", "maxLength": 1000 } } }, "required": [ "title", "description", "raw_attributes" ] } }, "target_taxonomies": { "minItems": 1, "type": "array", "items": { "type": "string", "enum": [ "google", "shopify", "amazon" ] } } }, "required": [ "products", "target_taxonomies" ], "$schema": "http://json-schema.org/draft-07/schema#" }
Connections
streamable-http
https://catalog-normalizer.acjlabs.com/mcp