filtrous-mcp-catalog
https://filtrous-mcp-catalog.filtrous.workers.dev
Registry code: 2814d903b7a42641
Search Filtrous lab-filtration products by spec, get prices, and request quotes from your AI agent.
from a public catalogue that lists it, not from the operator
- endpoint
- https://filtrous-mcp-catalog.filtrous.workers.dev/mcp
- 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 filtrous-mcp-catalog live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is filtrous-mcp-catalog free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does filtrous-mcp-catalog have?
- 4 tools: request_quote, get_price_and_lead_time, get_product_details, search_products.
- Is filtrous-mcp-catalog 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 4 tools
- degraded → live
- unknown → live
- used for
- search lab filtration products
- get product price and lead time
- request a quote
- takes → gives
- text → data
- tools
- 3 reads1 sends messages
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
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
request_quote sends messages unknown never probed
Submit a quote request for one or more SKUs with buyer contact info. KEYED tool — requires a valid API key. Sales follows up out-of-band.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "items", "contact" ], "properties": { "items": { "type": "array", "items": { "type": "object", "required": [ "sku", "quantity" ], "properties": { "sku": { "type": "string", "minLength": 1, "description": "Product SKU." }, "quantity": { "type": "integer", "maximum": 100000, "description": "Units requested.", "exclusiveMinimum": 0 } }, "additionalProperties": false }, "maxItems": 50, "minItems": 1, "description": "Line items to quote." }, "notes": { "type": "string", "description": "Free-text context / use case." }, "contact": { "type": "object", "required": [ "name", "email" ], "properties": { "name": { "type": "string", "minLength": 1, "description": "Requester name." }, "email": { "type": "string", "description": "Requester email." }, "phone": { "type": "string", "description": "Phone number." }, "company": { "type": "string", "description": "Company name." } }, "additionalProperties": false } }, "additionalProperties": false }arguments 69 linesget_price_and_lead_time reads unknown 12h ago
Get current price, availability, and (when permitted) stock for a SKU. KEYED tool — requires a valid API key. Tier pricing and lead time are placeholders until the Acumatica sync ships.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "sku" ], "properties": { "sku": { "type": "string", "description": "The exact product SKU." } }, "additionalProperties": false }arguments 14 linesget_product_details reads unknown 12h ago
Get full details for one product by its handle: variants, SKUs, options, prices, images, and spec metafields. Open tool — no API key required.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "handle" ], "properties": { "handle": { "type": "string", "description": "The product handle (slug), e.g. from search_products." } }, "additionalProperties": false }arguments 14 linessearch_products reads unknown 12h ago
Search the Filtrous catalog by free text and/or spec terms (e.g. '0.22 micron PES syringe filter'). Returns matching products with title, handle, SKU, product_type, tags, price, and availability. Open tool — no API key required.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "query" ], "properties": { "limit": { "type": "integer", "maximum": 50, "minimum": 1, "description": "Max results (default 10)." }, "query": { "type": "string", "description": "Free-text and/or spec search. Field filters like 'product_type:...' or 'tag:...' are also honored." } }, "additionalProperties": false }arguments 20 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 id2814d903b7a42641.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/2814d903b7a42641/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/2814d903b7a42641?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.