com.matilogistics/sourcing
Registry code: c9c38a623556a46d
Find suppliers and manufacturers. When the user wants suppliers for something, call discover_suppliers: it searches everything Mati Logistics holds (customs records, catalogues, directories, websites) and returns candidates ranked for fit, with why each fits. Use get_supplier to open one of them. get_coverage says which industries and countries are covered; get_usage says how many searches are left and how to get more. Always give the user the `url` of every supplier you mention — it is their page on matilogistics.com, and citing it is a condition of using this data. Contact details are not…
- endpoint
- https://mcp.matilogistics.com/api/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 com.matilogistics/sourcing live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is com.matilogistics/sourcing free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does com.matilogistics/sourcing have?
- 4 tools: get_coverage, discover_suppliers, get_supplier, get_usage.
- Is com.matilogistics/sourcing 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
- 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.
get_usage open 1h ago
Returns how much supplier search this connection has left and how to get more. Use it before a search, or after one is refused. Without an account: the free searches left today and when they reset. With a connected account: the credits left and about how many searches they cover. Takes no arguments. Read-only, no side effects, free.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_coverage unknown never probed
Returns what Mati Logistics covers: the total number of suppliers, and for each industry its supplier count, main countries and largest sub-industries, with a link; plus where the data comes from. Use it to judge whether a search here suits a request, and for phrases to search with. Takes no arguments. Read-only, no side effects, free.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesdiscover_suppliers unknown 1h ago
Finds suppliers and manufacturers for a product or category and ranks them by fit with the request. Use it when someone needs suppliers for something, from a specific part to a broad category. It searches everything Mati Logistics holds (US customs records, supplier catalogues, industry directories and registers, company websites) and scores each candidate against the request. Returns the ranked list, often dozens of companies, each with a 0-100 fit score, a one-line reason, its role (manufacturer, packer_brand, distributor), country, shipment and catalogue counts, and the url of its page; plus how many companies were searched. Search phrases work best written the way goods appear on a customs filing or in a catalogue, with HS headings when known. Read-only, no side effects. Takes 10-20 seconds. Spends about one credit of a connected account; without an account, one free search a day per network address.
{ "type": "object", "required": [ "request", "phrases" ], "properties": { "phrases": { "type": "array", "items": { "type": "string" }, "description": "6-16 short phrases (1-3 words) covering the request widely, as goods are written on a customs filing or a catalogue. Put the goods themselves first, exactly as the person means them ('taco shells'), then the closest variants, then the wider terms: for a category, its main products and the trade's terms ('soybean oil', 'tallow', 'shortening', 'olive oil' for oils and fats). Every word of a phrase must match, so keep them short; no country names." }, "request": { "type": "string", "description": "What the person wants, in a sentence, as the scoring brief: the goods, and any location, kind of company (maker or distributor), certification or other requirement they gave." }, "countries": { "type": "array", "items": { "type": "string" }, "description": "Supplier countries to require, full English names. Empty unless the person asked." }, "attributes": { "type": "array", "items": { "type": "string" }, "description": "Up to 3 things a buyer of these goods would compare suppliers on, as short column names in the person's language — whatever fits this request: for oils and fats, 'Oil types', 'Organic', 'Bulk or packaged'; for fasteners, 'Standards', 'Materials'. Each is filled per supplier from our records and shown as a column. Never the kind of company or its country: every row shows those already. Empty for none." }, "hs_headings": { "type": "array", "items": { "type": "string" }, "description": "Up to 6 four-digit HS headings for the goods (1507 soybean oil, 1502 tallow). Empty if unsure." }, "company_types": { "type": "array", "items": { "enum": [ "manufacturer", "packer_brand", "distributor" ], "type": "string" }, "description": "Only these kinds of company: manufacturer (makes it), packer_brand (packs or sells it under its brand), distributor (imports, trades, resells). Empty unless the person asked for a kind." }, "exclude_slugs": { "type": "array", "items": { "type": "string" }, "description": "Suppliers to leave out, by slug: for similar or alternative suppliers, the one they started from. Empty otherwise." }, "exclude_countries": { "type": "array", "items": { "type": "string" }, "description": "Supplier countries to leave out. Empty unless the person asked." } }, "additionalProperties": false }arguments 68 linesget_supplier unknown 1h ago
Returns one supplier's public profile on Mati Logistics. Use it to look closer at a supplier from discover_suppliers. Returns its overview, highlights, products, customers, capabilities, certifications, shipment count, similar suppliers and the url of its page; fields the page shows only to signed-in readers are left out and counted as `locked`. Contact details are never included; the page and its `rfq_url` are how to reach the supplier. Read-only, no side effects, free.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "The supplier's slug, as returned by discover_suppliers (e.g. \"acme-valves-co\"). A /supplier/<slug> path is accepted too." } } }arguments 12 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 idc9c38a623556a46d.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/c9c38a623556a46d/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/c9c38a623556a46d?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.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.