originselect
Related Servers
Alternatives to originselect
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceSearch URDB's product integrity database — integrity scores, enshittification events, warranty cuts, and material downgrades across consumer products. Sourced and evidence-backed.439 npm2MIT
- AlicenseAqualityAmaintenanceCross-border product catalog for AI agents. Search and compare products from US and South East Asian markets via Model Context Protocol.697 npm14MIT
- AlicenseNot gradedqualityDmaintenanceProvides tools for searching and filtering low-tox products on the Lowtoxgear storefront, and scanning product barcodes to analyze ingredients against chemical rules and condition-specific flags.MIT
- AlicenseNot gradedqualityAmaintenanceLook up food products by barcode, search by ingredient or nutrition filter, compare products side-by-side, and browse the canonical tag vocabulary via MCP.364 npm1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceSearch, verify and screen over 1 million African companies across 18 official government registries, along with the public contracts they have won and OFAC/UN sanctions screening. Every result carries its registry source, date and a confidence signal, and the server returns nulls rather than fabricating data.MIT
- FlicenseNot gradedqualityDmaintenanceDTC competitor intelligence: catalog snapshots, price history, cross-brand product comparison, and drop/restock detection for 84 Shopify-powered brands. Pay-per-call via Apify.-
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: three metadata enumerators (categories/countries/values), two distinct search targets (brands vs products), and one refinement operation. No functional overlap exists between any pair.
Perfectly consistent snake_case convention with clear verb_noun structure throughout: 'get_' prefix for metadata retrieval, 'search_' prefix for discovery operations, and 'refine_search' for the modification action.
Six tools is ideal for this focused search/discovery domain. The surface covers metadata discovery, primary search vectors (brands and products), and result refinement without bloat or missing core capabilities.
Strong coverage for a read-only search API: filtering dimensions are fully exposed via metadata endpoints, and both major entity types (brands/products) are searchable. Minor gap: refine_search appears product-specific with no equivalent brand refinement, and lacks single-item retrieval by ID (though search may suffice).