mattercatalog
Registry code: 16e3d4b86c3df254
MatterCatalog (mattercatalog.com) is an independent US catalog of Matter smart home devices. For each product it records whether it holds a CSA (Connectivity Standards Alliance) Matter certificate, with the certificate ID and date; its network (Thread, Wi-Fi or Ethernet) and whether that needs a Thread border router; the platforms its page lists (Apple Home, Amazon Alexa, Google Home, Samsung SmartThings); and store links matched to the exact model. check_matter_certification searches MatterCatalog's published read of the CSA Distributed Compliance Ledger by product name, brand, model, part…
- endpoint
- https://mattercatalog.com/api/mcp?src=mcp-registry
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is mattercatalog live?
- Yes — it answered the hub's last check (checked 29m ago). It answered 100% of checks over the last 30 days.
- Is mattercatalog free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does mattercatalog have?
- 5 tools: where_to_buy, compare, check_matter_certification, catalog_stats, find_matter_devices.
- Is mattercatalog safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 5 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
catalog_stats open 29m ago
MatterCatalog's dated figures as sentences that carry their own date: how many Matter certified product models and companies are on the CSA Distributed Compliance Ledger (MatterCatalog's read of it), how many distinct certificates, how many models were newly certified in the latest ledger week and month, and how many products MatterCatalog lists and sells in the US by certificate, network and platform, each with the MatterCatalog page that shows it. No arguments.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesfind_matter_devices open 29m ago
Lists Matter smart home products in MatterCatalog's catalog by category, platform, network and brand, with one line of facts each: the product page's certification answer (CSA certificate and date), network and whether it needs a Thread border router, the platforms its page lists, and the stores its page links (names only, no prices). By default only products sold in the US with a verified store link and a CSA certificate for the exact model. Includes the matching MatterCatalog buying guide's picks where one exists. Each product links to its MatterCatalog page.
{ "type": "object", "properties": { "brand": { "type": "string", "maxLength": 60, "description": "Brand, e.g. 'Aqara', 'Eve', 'TP-Link'." }, "limit": { "type": "integer", "default": 10, "maximum": 25, "minimum": 1, "description": "Products to return (1-25)." }, "network": { "enum": [ "Thread", "Wi-Fi", "Ethernet" ], "type": "string", "description": "Matter network. Thread devices need a Thread border router; Wi-Fi and Ethernet do not." }, "category": { "enum": [ "Air Purifiers", "Blinds", "Climate", "Fans", "Hubs", "Lighting", "Locks", "Other", "Plugs", "Remotes & Buttons", "Robot Vacuums", "Sensors", "Switches", "TVs", "Thermostats" ], "type": "string", "description": "Product category." }, "sold_in_us": { "type": "boolean", "default": true, "description": "true (default): only products sold in the US with a verified US store link; false adds records sold outside the US and reference records." }, "works_with": { "enum": [ "Apple Home", "Google Home", "Alexa", "SmartThings", "Home Assistant" ], "type": "string", "description": "Platform the product page lists (from the maker's own pages). Home Assistant is not recorded per product; with it, the answer explains how Home Assistant uses Matter and lists products by the other filters." }, "certified_only": { "type": "boolean", "default": true, "description": "true (default): only products with a CSA certificate for the exact model." } }, "additionalProperties": false }arguments 69 lineswhere_to_buy unknown never probed
Names the stores MatterCatalog's product page links for one product (store links matched to the exact model, pack and region), with the product's certification answer and network, and links that page, where the store buttons, prices with their check times and the affiliate disclosure are. Store names only: no store URLs and no prices. Takes a brand and model, a MatterCatalog product ID or a mattercatalog.com/product/ URL.
{ "type": "object", "required": [ "product" ], "properties": { "product": { "type": "string", "maxLength": 200, "minLength": 2, "description": "Brand and model (e.g. 'Eve Energy Smart Plug'), a MatterCatalog product ID or a mattercatalog.com/product/<id> URL." } }, "additionalProperties": false }arguments 15 linescompare unknown never probed
Compares two products from MatterCatalog's catalog side by side: brand, category, the product page's certification answer with certificate and date, CSA device type and Matter version, network (and whether it needs a Thread border router), the platforms each page lists, where each is sold and the stores its page links (names only, no prices), with links to both pages and to MatterCatalog's side-by-side compare page.
{ "type": "object", "required": [ "a", "b" ], "properties": { "a": { "type": "string", "maxLength": 200, "minLength": 2, "description": "First product: brand and model, MatterCatalog product ID or product page URL." }, "b": { "type": "string", "maxLength": 200, "minLength": 2, "description": "Second product, the same way." } }, "additionalProperties": false }arguments 22 linescheck_matter_certification unknown 29m ago
Checks whether a product holds a Matter certificate on the CSA (Connectivity Standards Alliance) Distributed Compliance Ledger, using MatterCatalog's published read of the ledger (the same index as its "Is it Matter certified?" lookup page). Takes a product name, brand, model, part number or CSA certificate ID. Returns the matching ledger models with certificate IDs, certification dates, software and Matter versions, CSA device type and network (Thread, Wi-Fi or Ethernet), the date of the ledger read, and the MatterCatalog product page with that page's own certification answer and store names where one exists; also MatterCatalog pages for matching products that are not on the ledger (bridged or claim-only). No prices.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "integer", "default": 5, "maximum": 10, "minimum": 1, "description": "How many ledger models to show (1-10)." }, "query": { "type": "string", "maxLength": 200, "minLength": 2, "description": "Product name, brand + model, part number or CSA certificate ID, e.g. 'Aqara U200', 'Eve Energy', 'Tapo P125M', 'CSA22084MAT40084-24'." } }, "additionalProperties": false }arguments 22 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id16e3d4b86c3df254.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/16e3d4b86c3df254/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/16e3d4b86c3df254?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.