This update is about search and about the MCP connector that AI assistants use to query our typed specification layer.
- Frequency conditions now work in search. A query such as X-band transmitter above 8 GHz, Ka-band antenna above 20 GHz or UHF radio below 500 MHz is now checked against each product’s operating band — the lowest and highest frequency in its specifications — instead of being ignored. More than 600 products in the catalogue carry a band. Ranges are compared the way an engineer would: above 8 GHz keeps a product whose band reaches above 8 GHz.
- Search starts when you ask. Results now load when you press Enter or the search button, not while you are still typing, so a half-typed phrase no longer produces half-relevant results.
- Search keeps working without a third party. The semantic index and a multilingual language model both run on our own server. If the external AI that reads the conditions of a query is unavailable, search keeps working, still recognises the kind of hardware you mean in dozens of languages, and says so on the page. Only numeric conditions such as under 1 kg wait until the query parser is back.
- A steadier MCP connector. The connector at
/mrd-connect/mcpnow also answers the stream-opening request that MCP clients and directories use to check that a server is alive. When an AI agent passes several component classes in one call,get_component_specsandmatch_componentsreturn the first class together with a note listing the others to request, instead of an empty result; an unknown class returns the list of valid ones.
Try it on search, or connect your assistant via Connect to MRD.